Hi Dave, Firstly thanks for taking a look at the stuff I sent yesterday (sorry about the verbosity also).
I followed your suggestions below - the first problem that occurs is: "/xalan1_9/build $ ../xml-xalan/c/runConfigure -p linux -c gcc -x g++" sets PLATFORM=UNKNOWN in Makefile.incl I manually set PLATFORM to LINUX in Makefile.incl and run gmake which errors out below ( hopefully not too verbose ) I don't want to have you spend too much time looking at my efforts so I guess my question is this: Is there any future plan to include interix in the xalan-c build scipts much the same way xerces-c includes it? or is that someone elses reponsiblity e.g. individual user (me) or perhaps interix folk etc... just as an fyi, Interix is now free and as of 2003 Server R2 is no longer an add-on - it will come as a built in Windows component so I imagine a lot of folk in the future would find it useful if xalan-dev included in it in the build scripts. I understand it is probably not on anyone's radar yet, just looking for an idea as to whether the development group have considered it. I do appreciate your help so thanks again in advance Ian % gmake gmake -C src/xalanc all gmake[1]: Entering directory `/xalan1_9/build/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/build/src/xalanc/Utils' mkdir -p ../../../nls mkdir -p ../../../nls/include gmake[2]: Leaving directory `/xalan1_9/build/src/xalanc/Utils' gmake -C Utils locale gmake[2]: Entering directory `/xalan1_9/build/src/xalanc/Utils' gmake -C MsgCreator gmake[3]: Entering directory `/xalan1_9/build/src/xalanc/Utils/MsgCreator' g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/MsgFileOutpu tStream.o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/MsgFileOutputStream. cpp g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/ICUResHandle r.o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/ICUResHandler.cpp g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/InMemHandler .o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/InMemHandler.cpp g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/MsgCreator.o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/MsgCreator.cpp g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/NLSHandler.o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/NLSHandler.cpp g++ -O2 -DNDEBUG -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRAN T -D XALAN_INMEM_MSG_LOADER -c -I/xalan1_9/xml-xalan/c/src -I/xalan1_9/xml-xalan/ c/in clude -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/SAX2Handler. o /xalan1_9/xml-xalan/c/src/xalanc/Utils/MsgCreator/SAX2Handler.cpp g++ -DLINUX -fPIC -DXALAN_INMEM_MSG_LOADER \ -L/usr/local/lib -L/xerces-c-src_2_6_0/lib -lxerces-c ../../../../obj/MsgFile OutputStream.o ../../../../obj/ICUResHandler.o ../../../../obj/InMemHandler.o .. /../../../obj/MsgCreator.o ../../../../obj/NLSHandler.o ../../../../obj/SAX2Hand ler.o -o ../../../../bin/MsgCreator /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3/../../../../i586-pc-interix3/b in/l d: BFD 2.13.90 20021111 assertion fail /dev/fs/C/gnu2.intel/egcs.source/bfd/coff link.c:5211 /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3/../../../../i586-pc-interix3/b in/l d: BFD 2.13.90 20021111 assertion fail /dev/fs/C/gnu2.intel/egcs.source/bfd/coff link.c:5211 /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3/../../../../i586-pc-interix3/b in/l d: BFD 2.13.90 20021111 assertion fail /dev/fs/C/gnu2.intel/egcs.source/bfd/coff link.c:5211 /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3/../../../../i586-pc-interix3/b in/l d: BFD 2.13.90 20021111 assertion fail /dev/fs/C/gnu2.intel/egcs.source/bfd/coff link.c:5211 gmake[3]: Leaving directory `/xalan1_9/build/src/xalanc/Utils/MsgCreator' ../../../bin/MsgCreator /xalan1_9/xml-xalan/c/src/xalanc/NLS/en_US/XalanMsg_en_U S.xlf -TYPE INMEM -LOCALE en_US gmake[2]: *** [../../../nls/include/LocalMsgData.hpp] Segmentation fault (core d umped) gmake[2]: Leaving directory `/xalan1_9/build/src/xalanc/Utils' gmake[1]: *** [locale] Error 2 gmake[1]: Leaving directory `/xalan1_9/build/src/xalanc' gmake: *** [all] Error 2 % > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
