[fdo-users] FDO Compile error (libxalan-c)
john.spitzer at gmail.com
Tue Oct 6 01:49:23 EDT 2009
When building FDO from source on Ubuntu I got the following g++
compile time issue:
g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX
-D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c
In member function ‘xalanc_1_7::XalanDOMString&
error: ‘memmove’ is not a member of ‘std’
In static member function ‘static size_t
error: ‘strlen’ is not a member of ‘std’
In function ‘bool xalanc_1_7::doTranscodeFromLocalCodePage(const
char*, size_t, bool, xalanc_1_7::XalanDOMCharVectorType&, bool)’:
error: ‘strncpy’ is not a member of ‘std’
make: *** [../../obj/XalanDOMString.o] Error 1
make: Leaving directory
make: *** [all] Error 2
This was fixed by including in the source of
the following include directive :
There are quite a few cases where this is necessary to achieve a clean
compile of xml-xalan.
gcc/g++ is the standard compiler on Linux.
The passage of environment variables between shell script is a famous
Unix gotcha. I did not bother to Google it, but you can give it a try
to get some background on this issue.
What really causes most grief in migrating systems developed under
Windows onto Unix is case-sensitivites of system names(File names etc)
- windows is case insensitive while unix is case sensitive.
Hope this is of some assistance,
On Tue, Oct 6, 2009 at 4:08 PM, kernel_panic
<sudoaptgetinstalld00d3 at gmail.com> wrote:
> Hi, John
> When you say
>> "The First(FDO) stage requires for gdl, sdf, shp, ogr some fixes in
>> xml-xalan - looks like something you get for free with visual studio
>> has to be spelled out in gcc (#include <cstring>) in a number of
>> places in the code. Also in the gdal sub-build there some issues with
>> passing environment variables between shell scripts - a well known
>> trap which can cause grief - I did a hack to get it to work - I do not
>> remember what the optimal solution is as it was a long time ago."
> What kind of stuff are you talking about, regarding to visual studio, gcc
> and the passing environment variables issues?
> I mean, you dont have to tell me "do this, do that and done", but if you can
> give me a hint (or anyone else :p) on what to look for and where, I might
> get a greater insight on this, and perhaps, find a solution by narrowing the
> possible causes of this problem.
> Heh, for a "well known" problem, solution remains "unknown", because this is
> the second time I read that someone has fixed this, cant dont remember how
> Thanks for the reply!
> fdo-users mailing list
> fdo-users at lists.osgeo.org
More information about the fdo-users