Am Fri, 29 Sep 2006 11:30:13 -0700 schrieb David Bertoni <[EMAIL PROTECTED]>:
> Thomas Porschberg wrote: > > Am Fri, 29 Sep 2006 09:01:09 -0700 > > schrieb David Bertoni <[EMAIL PROTECTED]>: > > > >> Thomas Porschberg wrote: > >>> Hi, > >>> > >>> I tried that. I changed the XALANCROOT to a Windows path form and > >>> did the changes you suggest. > >>> I still had to create a link for the xerces lib otherwise I got > >>> an error that the linker is unable to find libxerces-c. > >>> I set a link from cygwins libxerces-c25.ddl.a to libxerces-c.dll.a > >>> Now I got linker errors: > >>> g++ -O -DNDEBUG -fno-elide-constructors -Wall -DCYGWIN > >>> -D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c > >>> -IC:\cygwin\usr\src\xml-xalan\c/src > >>> -IC:\cygwin\usr\src\xml-xalan\c/include -I../../../../nls/include > >>> -I/src/ -I/include/xercesc -I/include/ > >>> -o ../../../../obj/NLSHandler.o > >>> C:\cygwin\usr\src\xml-xalan\c/src/xalanc/Utils/MsgCreator/NLSHandler.cpp^M > >>> g++ -O -DNDEBUG -fno-elide-constructors -Wall -DCYGWIN > >>> -D_REENTRANT -DXALAN_INMEM_MSG_LOADER -c > >>> -IC:\cygwin\usr\src\xml-xalan\c/src > >>> -IC:\cygwin\usr\src\xml-xalan\c/include -I../../../../nls/include > >>> -I/src/ -I/include/xercesc -I/include/ > >>> -o ../../../../obj/SAX2Handler.o > >>> C:\cygwin\usr\src\xml-xalan\c/src/xalanc/Utils/MsgCreator/SAX2Handler.cpp^M > >>> g++ -DCYGWIN -DXALAN_INMEM_MSG_LOADER \^M -L/lib > >>> -lxerces-c ../../../../obj/MsgFileOutputStream.o > >>> ../../../../obj/ICUResHandler.o ../../../../obj/InMemHandler.o > >>> ../../../../obj/MsgCreator.o ../../../../obj/NLSHandler.o > >>> ../../../../obj/SAX2Handler.o > >>> -o ../../../../bin/MsgCreator -L/lib -lxerces-c^M Info: resolving > >>> xercesc_2_5::XMLUni::fgXercescDefaultLocale by linking to > >>> __imp___ZN11xercesc_2_56XMLUni22fgXercescDefaultLocaleE > >>> (auto-import) Info: resolving > >>> xercesc_2_5::XMLPlatformUtils::fgMemoryManager by linking to > >>> __imp___ZN11xercesc_2_516XMLPlatformUtils15fgMemoryManagerE > >>> (auto-import) Info: resolving > >>> xercesc_2_5::XMLUni::fgSAX2CoreValidation by linking to > >>> __imp___ZN11xercesc_2_56XMLUni20fgSAX2CoreValidationE > >>> (auto-import) Info: resolving > >>> xercesc_2_5::XMLUni::fgXercesDynamic by linking to > >>> __imp___ZN11xercesc_2_56XMLUni15fgXercesDynamicE (auto-import) > >>> Info: resolving xercesc_2_5::XMLUni::fgSAX2CoreNameSpaces > >>> by linking to > >>> __imp___ZN11xercesc_2_56XMLUni20fgSAX2CoreNameSpacesE > >>> (auto-import) Info: resolving > >>> xercesc_2_5::XMLUni::fgXercesSchema by linking to > >>> __imp___ZN11xercesc_2_56XMLUni14fgXercesSchemaE (auto-import) > >>> Info: resolving xercesc_2_5::XMLUni::fgXercesSchemaFullChecking > >>> by linking to > >>> __imp___ZN11xercesc_2_56XMLUni26fgXercesSchemaFullCheckingE > >>> (auto-import) Info: resolving > >>> xercesc_2_5::XMLUni::fgSAX2CoreNameSpacePrefixes by linking to > >>> __imp___ZN11xercesc_2_56XMLUni27fgSAX2CoreNameSpacePrefixesE > >>> (auto-import) make.exe[3]: Leaving directory > >>> `C:/cygwin/usr/src/xml-xalan/c/src/xalanc/Utils/MsgCreator'^M > >>> ../../../bin/MsgCreator > >>> C:/cygwin/usr/src/xml-xalan/c/src/xalanc/NLS/en_US/XalanMsg_en_US.xlf > >>> -TYPE inmem -LOCALE en_US^M make.exe[2]: *** > >>> [../../../nls/include/LocalMsgData.hpp] Error 128^M make.exe[2]: > >>> Leaving directory > >>> `C:/cygwin/usr/src/xml-xalan/c/src/xalanc/Utils'^M make.exe[1]: > >>> *** [locale] Error 2^M make.exe[1]: Leaving directory > >>> `C:/cygwin/usr/src/xml-xalan/c/src/xalanc'^M > >>> C:\cygwin\bin\make.exe: *** [all] Error 2^M > >> These ^Ms are a bit troublesome. I would not expect to see > >> carriage returns in the tar version of the repository. Did you do > >> Unix to DOS linefeed translation at some point? > > > > I used the ming32-make as make tool because the cygwin make did not > > work. And what I posted here was simply the redirected Make-output > > from make 1>mylog 2>&1 > > And I think the minw32-make produced the ^Ms. > > Or do I misunderstand something. > > I leave the office now but I'm still interested in solving this > > problem. > > > > I'm not sure mixing the ming make utility and Cygwin is a good idea. > > >>> New try with a new link for xerces. libxerces-c.ddl.a pointed now > >>> to the 2.7-er xerces lib I installed as binary. But I got again > >>> linker errors. > >>> > >>> g++ -DCYGWIN -DXALAN_INMEM_MSG_LOADER \ > >>> -L/lib > >>> -lxerces-c ../../../../obj/MsgFileOutputStream.o ../../../../obj/ICURes > >>> Handler.o ../../../../obj/InMemHandler.o ../../../../obj/MsgCreator.o > >>> ../../../. > >>> ./obj/NLSHandler.o ../../../../obj/SAX2Handler.o > >>> -o ../../../../bin/MsgCreator - > >>> L/lib -lxerces-c > >>> ../../../../obj/MsgFileOutputStream.o:MsgFileOutputStream.cpp:(.text+0x505): > >>> und > >>> efined reference to `xercesc_2_5::XMLString::transcode(char > >>> const*)' > >>> > >>> Seems hard to compile Xalan by myself. > >>> Still any hints ? > >> Well, the current code in the repository works fine, but I'll give > >> 1.10 a try, just to see how it works for me. > >> > >> Dave > >> > > I downloaded xerces-c-src_2_7_0.tar.gz and built it successfully. I > then downloaded Xalan-C_1_10_0-src.tar.gz and built it successfully > as well. > > I would not recommend mixing Xerces-C 2.5 with Xalan-C 1.10. I don't > know how Cygwin actually packages Xerces-C, so you should probably > build Xerces-C 2.7 locally, and use that version. > Hi, thank you for the advice. I compiled now xerces-c-src_2_7_0.tar.gz with cygwin make and I deinstalled xerces-2.5 from cygwin. Next step was to install Xalan. I set XERCESCROOT=/usr/src/xerces-c-src_2_7_0 and XALANCROOT=C:\cygwin\usr\src\xml-xalan\c and for Xalan compilation I had to use the Mingw-Make. Compile started but I got an error in TestXPath/testXParg.cpp and other sources that xalan/Include/PlatformDefinitions.hpp cannot be found. The file exist in src/xalanc/Include but it seems not found(wrong Inlucde path). Do I have to adopt some Include paths ? Thomas --
