On Sat, Aug 30, 2008 at 01:36, David Bertoni <[EMAIL PROTECTED]> wrote: > Neither Xalan-C 1.10 nore Xerces-C 2.8 are compatible with ICU 3.8.1 if you > use the ICU message loading option. You should use ICU 3.2 1 instead, or > make sure you build both libraries with -m inmem.
The following runConfigure calls were used to build ICU, Xerces and Xalan: ICU: ./runConfigureICU --enable-debug Linux --prefix=/home/ckuehlin/icu381 Xerces: ./runConfigure -p linux -c gcc -x g++ -d -t icu -b 32 -l -L/home/ckuehlin/icu381/lib -P /home/ckuehlin/xerces28bin Xalan ./runConfigure -p linux -c gcc -x g++ -t icu -r pthread -b 32 -l -L/home/ckuehlin/xerces28bin/lib -l -L/home/ckuehlin/icu381/lib -P /home/ckuehlin/xalan110bin Relevant environment parameters were export XERCESCROOT=/home/ckuehlin/xerces28src/xerces-c-src_2_8_0 export ICUROOT=/home/ckuehlin/icu381 export XALANCROOT=/home/ckuehlin/xalan110src/xml-xalan/c export XALAN_USE_ICU=true > Can you be more specific about what version of SUSE you're running? It's Opensuse 10.3 with its default packages. (Both gcc and g++ 4.2.1) I am able to reproduce the problem with the default packages of icu, xerces and xalan of this distribution. (ICU 3.6, Xerces 2.7.0, Xalan 1.10) I have the remote suspicion that somehow the initializers get invoked more than once (bypassing the project's central initializer singleton) but I have to investigate this further in order to come up with a small example exhibiting the same behaviour. Christian
