> As suggested, I grabbed the latest tarball. It got a > little further, but: > > g++ -O2 -DNDEBUG -fno-elide-constructors -Wall > -fPIC -DLINUX -D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c > -I/export/00/compiles/xml-xalan/c/src > -I/export/00/compiles/xml-xalan/c/include > -I../../nls/include > -I/export/00/compiles/xerces-c-src_2_6_0/src/ > -I/export/00/compiles/xerces-c-src_2_6_0/include/xercesc > -I/export/00/compiles/xerces-c-src_2_6_0/include/ -o > ../../obj/TestXPath.o > /export/00/compiles/xml-xalan/c/src/xalanc/TestXPath/TestXPath.cpp > /export/00/compiles/xml-xalan/c/src/xalanc/TestXPath/TestXPath.cpp:
That's the danger with the latest tarball -- you don't know when the snapshot was taken, and this one was caught between two checkins. You can either apply the patches from here: http://marc.theaimsgroup.com/?l=xalan-cvs&m=111420892300594&w=2 http://marc.theaimsgroup.com/?l=xalan-cvs&m=111420892911461&w=2 Or, you can just do a checkout of the source via anonymous CVS: http://xml.apache.org/cvs.html#AnonCVS If you do that, you'll be able to keep up with patches, should you have any more problems building. I have a build on Fedora core 3 with gcc 3.4.2 running right now. If I find any other problems with the latest CVS code, you should see patches on the xalan-cvs list later today. Dave
