I've got no idea why you would get multiple versions of standard libraries,
unless your compiler installation is broken.
If you look at the Makefile, you'll see that we don't link against any
explicit version of those libraries. Here's what I get on my RedHat 6.1
box:
~/apache/xml-xalan/c/bin > ldd testXSLT
libxalan-c1_3.so =>
/home/xalan/apache/xml-xalan/c/lib/libxalan-c1_3.so (0x40013000)
libxerces-c1_6_0.so =>
/home/xalan/apache/xerces-c1_6_0-linux/lib/libxerces-c1_6_0.so (0x40497000)
libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2
(0x40797000)
libm.so.6 => /lib/libm.so.6 (0x407d9000)
libc.so.6 => /lib/libc.so.6 (0x407f5000)
libpthread.so.0 => /lib/libpthread.so.0 (0x408e8000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
~/apache/xml-xalan/c/bin >
You might try leaving the ICU out of the mix, to see if that's the culprit.
Dave
|---------+------------------------------------>
| | Christopher Kelly |
| | <[EMAIL PROTECTED]|
| | oo-inc.com> |
| | |
| | 03/26/2002 04:32 AM |
| | Please respond to |
| | xalan-dev |
| | |
|---------+------------------------------------>
>----------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: xalan c on freebsd
|
>----------------------------------------------------------------------------------------------------------|
hello
i'm trying to get xalan-c version 1.3 to build on freebsd.
i can build the shared library and test programs, but they are useless as
they
depend on multiple/different versions of libc, libm and libstdc++ than i
have
on my system:
[[EMAIL PROTECTED] portalid_admin]$ ldd
~/dev/yahoo/external/xml-xalan/bin/testXPath
/homes/cck197/dev/yahoo/external/xml-xalan/bin/testXPath:
libxalan-c1_3.so => /home/y/lib/libxalan-c1_3.so (0x2806f000)
libxerces-c1_6_0.so => /home/y/lib/libxerces-c1_6_0.so (0x284f2000)
libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x287fb000)
libm.so.2 => /usr/lib/libm.so.2 (0x28841000)
libc.so.4 => /usr/lib/libc.so.4 (0x2885c000)
libc_r.so.4 => /usr/lib/libc_r.so.4 (0x288f1000)
libstdc++-libc6.1-1.so.2 => not found (0x0)
libm.so.6 => not found (0x0)
libc.so.6 => not found (0x0)
libicuuc.so.18 => /home/y/lib/libicuuc.so.18 (0x289a3000)
libicudata.so => /home/y/lib/libicudata.so (0x28a0e000)
libstdc++.so.2.10 => /home/y/lib/libstdc++.so.2.10 (0x291af000)
here's the output of ldd for a program built against xerces:
[[EMAIL PROTECTED] portalid_admin]$ ldd main
main:
libxerces-c1_6_0.so => /home/y/lib/libxerces-c1_6_0.so (0x280d1000)
libycore++.so.2 => /home/y/lib/libycore++.so.2 (0x283da000)
libstdc++.so.2.10 => /home/y/lib/libstdc++.so.2.10 (0x284f5000)
libm.so.2 => /usr/lib/libm.so.2 (0x2853e000)
libc_r.so.4 => /usr/lib/libc_r.so.4 (0x28559000)
libicuuc.so.18 => /home/y/lib/libicuuc.so.18 (0x2860b000)
libicudata.so => /home/y/lib/libicudata.so (0x28676000)
libyintl.so.1 => /home/y/lib/libyintl.so.1 (0x28e17000)
libysecure.so.1 => /home/y/lib/libysecure.so.1 (0x2903e000)
libycore.so.1 => /home/y/lib/libycore.so.1 (0x2904b000)
libcrypto.so.2 => /home/y/lib/libcrypto.so.2 (0x290b1000)
libssl.so.2 => /home/y/lib/libssl.so.2 (0x29168000)
libc.so.4 => /usr/lib/libc.so.4 (0x29195000)
so my question is this: what is causing the linker to create dependencies
to
lib{m,c}.so.6, libstdc++-libc6.1-1.so.2 and libstdc++.so.2.10?
as i'm already using xerces, i'm loathed to used a different xlst engine
that
will build on freebsd, eg. sablotron, so getting xalan to build would be
fantastic.
any help would be greatly appreciated.
chris.
--
christopher kelly <[EMAIL PROTECTED]>
yahoo! enterprise solutions, 10 ebury bridge road, london, sw1w 8pz
pgp public key: http://kuffworks.com/cck.pgp
tel: +44 (0)207 808 4525
gsm: +44 (0)7796 688 050
