Hi! > Downloaded Xalan-C_1_3-linux.tar.gz; tar'd it to the disk; removed " > -instances=static" from Makefile.in; and started > following the Xalan-C++ Release Notes. Well into the build, I got the > following error:
> Thought I'd ask if anyone's has already seen (and fixed) this before I > start digging around in the code. I didn't get this error. I downloaded Xerces 1.7 and got the current Xalan sources from CVS (see http://xml.apache.org/cvs.html for details on how to access CVS). The first step was to build Xerces: sh>export XERCESCROOT=/my/directory/to/xerces/xml-xerces/c sh>cd $XERCESCROOT/src/xercesc sh>./runConfigure -p linux -c gcc -x g++ -r pthread -m inmem -n socket -t native sh>make The next step is to build Xalan (XERCESCROOT must still be set!) sh>export XALANCROOT=/my/directory/to/xalan/xml-xalan/c sh>cd $XALANCROOT/src sh>./runConfigure -p linux -c gcc -x g++ -r pthread sh>make That was all I had to do to (re)build Xalan and Xerces. I used gcc 2.95.3 on SuSE 7.x (kernel 2.2.16). One last tip: I downloaded all files to a Windows machine and then transferred them to the linux box. All files had Windows line endings (\r\n) instead of unix line endings (just \n), so I ran into many, many errors until I discovered this problem and converted all files to have unix line endings. It doesn't matter for C(++) and header files (as long as you don't have string constants exceeding line breaks...) but it does matter for config* and Makefiles! A solution for this problem is to transfer all files to the linux machine using (s)ftp in ASCII mode or to use some conversion utility like tr. (BTW: vi shows windows line endings as ^M) Hope that helps. Ciao Wolfgang -- Wolfgang Schell [EMAIL PROTECTED] GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
