[fdo-users] FDO Compile error (libxalan-c)

[kernel_panic]

Well, right now Im using 3.3.1, but I might give 3.4.0 a go :)

Now, I have some more questions :)

a) Have you compiled FDO succesfully on ubuntu (or anything
debian-based)? if so, which version, and how did you do it?
b) Do you know which FDO providers work with CMake build system?
c) How do I try using CMake? :p. Never been there, never done that :p

2009/10/6, Traian Stanev <traian.stanev at autodesk.com>:
>
> Hi,
>
> If you are using the latest Ubuntu and the latest FDO sources, your best bet
> is probably to try the CMake build system instead of the automake based one.
> That of course depends on which FDO providers you need, since some of them
> don't have CMake files yet.
>
> Traian
>
>
>
>> -----Original Message-----
>> From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-
>> bounces at lists.osgeo.org] On Behalf Of kernel_panic
>> Sent: Tuesday, October 06, 2009 4:42 PM
>> To: FDO Users Mail List
>> Subject: Re: [fdo-users] FDO Compile error (libxalan-c)
>>
>> Well, Im not having this particular issue:
>>
>> 2009/10/6, john spitzer <john.spitzer at gmail.com>:
>> > Hi,
>> > 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
>> > -I/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xalan/c/src
>> > -I/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xalan/c/include
>> > -I../../nls/include
>> > -I/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xerces/c/src/
>> > -I/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xerces/c/include/xercesc
>> > -I/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xerces/c/include/  -o
>> > ../../obj/XalanDOMString.o
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:
>> > In member function 'xalanc_1_7::XalanDOMString&
>> > xalanc_1_7::XalanDOMString::assign(const xalanc_1_7::XalanDOMString&,
>> > size_t, size_t)':
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:281:
>> > error: 'memmove' is not a member of 'std'
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:
>> > In static member function 'static size_t
>> > xalanc_1_7::XalanDOMString::length(const char*)':
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:825:
>> > error: 'strlen' is not a member of 'std'
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:
>> > In function 'bool xalanc_1_7::doTranscodeFromLocalCodePage(const
>> > char*, size_t, bool, xalanc_1_7::XalanDOMCharVectorType&, bool)':
>> > /home/jjs/OpenSource_FDO/Thirdparty/apache/xml-
>> xalan/c/src/xalanc/XalanDOM/XalanDOMString.cpp:1154:
>> > error: 'strncpy' is not a member of 'std'
>> > make[1]: *** [../../obj/XalanDOMString.o] Error 1
>> > make[1]: Leaving directory
>> > `/home/jjs/OpenSource_FDO/Thirdparty/apache/xml-xalan/c/src/xalanc'
>> > make: *** [all] Error 2
>> >"
>>
>> But adding #include <cstring> on all  .cpp files on
>> /Thirdparty/gdal/frmts/ilwis/ made another (unnoticed :p) error go
>> away, regarding libgdal.so not being created.
>>
>> However, Im still getting the xalan error :S
>>
>> "make[1]: se sale del directorio `/opt/fdo-3.3.1/Thirdparty/gdal/apps'
>> make[1]: se ingresa al directorio `/opt/fdo-3.3.1/Thirdparty'
>> make[1]: *** No hay ninguna regla para construir el objetivo
>> `apache/xml-xalan/c/lib/libxalan-c.so.17.0', necesario para `all-am'.
>> Alto.
>> make[1]: se sale del directorio `/opt/fdo-3.3.1/Thirdparty'
>> make: *** [install-recursive] Error 1"
>>
>> I was thinking on what you said about passing variables between
>> scripts, but I dont know how the scripts are run :p, I mean, I dont
>> know who calls who, so I dont know where to look for...
>>
>> Does anyone know in which order the scripts are run, or how can I
>> figure out that?
>> _______________________________________________
>> fdo-users mailing list
>> fdo-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fdo-users
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
>