> Thanks, I tried that (output below) but there appears to be a source file > missing "LocalMsgIndex.hpp" > Is this a script generated header that somehow is not getting created > because i'm pretending the platform is linux but it's detecting interix > somewhwere?
First of all, please try to refrain from posting so much compiler/diagnostic ouput. If you edit the output to only include the relevant portions, it will make it much easier to respond. > In future, you may also directly type the following commands to create the > Makefiles. > > export TRANSCODER="NATIVE" > export MESSAGELOADER="INMEM" > export NETACCESSOR="Socket" > export THREADS="pthread" > export BITSTOBUILD="32" > export CC="gcc" > export CXX="g++" OK, this looks like the output from Xerces-C's runConfigure script and not Xalan-C's. Is this really the output of our runConfigure script. Note that if you've already got these environment variables defined from creating Xerces-C, they might interfere with Xalan-C's runConfigure. > % gmake > gmake -C src/xalanc all > gmake[1]: Entering directory `/xalan1_9/xml-xalan/c/src/xalanc' > Preparing the directory structure for a build ... > mkdir -p ../../obj > mkdir -p ../../lib > mkdir -p ../../bin > gmake -C Utils prepare > gmake[2]: Entering directory `/xalan1_9/xml-xalan/c/src/xalanc/Utils' > gmake[2]: Nothing to be done for `prepare'. > gmake[2]: Leaving directory `/xalan1_9/xml-xalan/c/src/xalanc/Utils' > gmake -C Utils locale > gmake[2]: Entering directory `/xalan1_9/xml-xalan/c/src/xalanc/Utils' > gmake[2]: Nothing to be done for `locale'. > gmake[2]: Leaving directory `/xalan1_9/xml-xalan/c/src/xalanc/Utils' It very strange that the MsgCreator executable is not built. > g++ -w -O -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C > -DPROJ_SAX2 -DPROJ_DOM -DPROJ_DEPRECATED_DOM -DPROJ_VALIDATORS > -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS > -DXML_USE_NETACCESSOR_SOCKET -fno-elide-constructors -Wall -fPIC -DINTERIX > -D_REENTRANT -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/c/include > -I../../nls/include -I/xerces-c-src_2_6_0/src/ > -I/xerces-c-src_2_6_0/include/xercesc -I/xerces-c-src_2_6_0/include/ -o > ../../obj/XalanAttr.o /xalan1_9/xml-xalan/c/src/xalanc/XalanDOM/XalanAttr.cpp Many of these are Xerces-C compiler flags, and they should not be there. Something went very wrong with the execution of Xalan-C's runConfigure script. > In file included from > /xalan1_9/xml-xalan/c/src/xalanc/PlatformSupport/PlatformSupportInit.cpp:22: > /xalan1_9/xml-xalan/c/src/xalanc/PlatformSupport/XalanMessageLoader.hpp:28:2 > 9: LocalMsgIndex.hpp: No such file or directory LocalMsgIndex.hpp is created by the MsgCreator executable at the beginning of the build. Given that executable did not build, I'm not surpised this file is missing. Something is very wrong with your environment and source distribution. Try the following: 1. Download a fresh nightly tarball, or checkout a fresh local copy of the source files, if you're using the cvs repository. 2. Start with a new shell that has no Xerces-C environment variables defined. 3. Make sure you define the XERCESCROOT and XALANCROOT environment variables properly. From your post, it looks like they are defined correctly, but just make sure. 4. Xalan-C is happy to build outside of the source directory, which is a very nice thing. Create a build directory and execute the runConfigure script from there. For example, if you create a "build" directory in "/xalan1_9": /xalan1_9/build $ ../xml-xalan/c/runConfigure -p linux -c gcc -x g++ ... gmake ... Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
