Hi David and all. I tried the perl script for building ICU and Xerces together. Ran into problems with the perl script too - hope you can help.
I exported three variables: export XERCESCROOT=/PEBuilds/bldtogether/xerces-c-src_2_7_0 export ICUROOT=/PEBuilds/bldtogether/icu export XERCESC_NLS_HOME=/PEBuilds/bldtogether/xerces-c-src_2_7_0/msg Note that this third directory does NOT exist as part of the xerces-c-current.tar.gz file and I did not create it. I only exported this third variable because the directions for building xerces via the perl script said to do it. I also edited the Xerces files to make them build a single-threaded version as per the documents online. My perl script execution line: perl packageBinaries.pl -s $XERCESCROOT -o /PEBuilds/bldtogether/build -t icu -m icu -c xlc -x xlC -r none -b 32 Log available here: http://www.electronicfiles.net/files/3560/myperlbuild.zip Note: I have no idea how to make the perl script comple ICU for single threading - something for the documentation? Or does putting the "-r none" on the command line do single threading for both xerces and icu? Anyway, the result of the perl script: The target directory - /PEBuilds/bldtogether/build - has the following directories empty: /PEBuilds/bldtogether/build/bin /PEBuilds/bldtogether/build/etc /PEBuilds/bldtogether/build/lib /PEBuilds/bldtogether/build/msg After going to /PEBuilds/bldtogether/build/samples and running: runConfigure -paix -cxlc -xxlC -rnone -b32 ...I ran gmake. The gmake output is in the same samples file. It can't find the library "xerces-c". Help? - Phil -----Original Message----- From: David Bertoni [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 11:34 AM To: [email protected] Subject: Re: CAN ANYBODY HELP ME? NOBODY RESPONDED TO MY POST THREE WEEKS AGO Schlesinger, Philip wrote: > Alberto, > > Thank you for responding back. To answer your questions (three parts): > >> 2) there is no log file at the address you specified >> (http://s19.quicksharing.com/v/6542260/xerces_logs.zip.html) >> nor at http://s19.quicksharing.com/v/6542260/xerces_logs.zip > > Quicksharing appears to be having issues. I've re-uploaded the logs > here: > http://www.electronicfiles.net/files/3560/xerces_logs.zip > > >> 3) Makefile.incl does specify for AIX the "32" and "26" suffixes, so >> you will have to update them (or remove them, as the other platform >> don't specify them) > > I will try just commenting out that entire section. However, why > would the developers put that in there for AIX in the first place? They are there because AIX binaries are not in ELF format, so there is no notion of an SONAME in the binary. If you link with icuuc.a, for example, your binary will contain a hard link to "icuuc.a" which is probably not what you want. > > Also FYI: I tried changing "32" entries to "34" entries (ex: > libicuuc32.0 => libicuuc34.1) and got the following munch error as > you'll see in the log files: > > <snip> > makeC++SharedLib -p 5000 -o > /PEBuilds/bldxerces/xerces-c-src_2_7_0/lib/libxerces-c27.0.a > AIX/AIXPlatformUtils.o AIX/ASCIIRangeFactory.o AIX/AbstractDOMParser.o > AIX/AbstractNumericFacetValidator.o ... ... > -L/PEBuilds/bldicu/icu/source/lib -L/PEBuilds/bldicu/icu/source/data > -L/PEBuilds/bldxerces/xerces-c-src_2_7_0/lib -L/usr/lpp/xlC/lib > -licuuc34 -licudata34 -lXercesMessages27 > munch: The input file /PEBuilds/bldicu/icu/source/lib/libicuuc34.a is > not valid in the current object mode. > /usr/vacpp/bin/makeC++SharedLib: 1543-303 Error during munch phase > gmake[1]: *** > [/PEBuilds/bldxerces/xerces-c-src_2_7_0/lib/libxerces-c27.0.a] Error 5 > </snip> > > Creating dynamic links for imaginary "32" files (ln -s libicuuc34.1.a > libicuuc32.a) caused the same munch error. > The munch error is because some of your binaries are 64-bit and some are 32-bit. From the makeC++SharedLib command it looks like you have 64-bit ICU binaries, and 32-bit Xerces-C binaries. >> 4) sorry, I don't have access to an AIX machine, >> so I cannot help you further. > > Anybody with AIX machine out there? > I will try to help, but I encourage you to try using the packageBinaries.pl script with the proper options to build a 64-bit binary without threads. Dave
