-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
i'm trying to build xerces-c against some sort of cross compile environment
which is simply a path with a different glibc and gcc and some toolchain.
It't not really a cross compile since I run that stuff on the same system with
a different ld-linux.so.2.
Background is, I'm developing on Fedora Core 2 glibc 2.3x / gcc 3.3x for a
older gcc2.95/glibc2.2 System.
That works fine already with all necessary libs but still xerces-c causes
problems. The reason seems to be that I can't force it to build using a
specific ld-linux.so dynamic linker.
Usually I use -Wl,--dynamic-linker=/cross/lib/ld-linux.so.2 to dynamically
link all my toolchain against the cross-glibc but that doesn't work for
xerces-c. ldd sais, the xerces libs have no dependencies outside /cross
but it seems to be looking for a glibc2.3 tag which is obviously not there
since it isn't a glibc2.3
$ ldd /cross/lib/libxerces-c.so
/cross/lib/libxerces-c.so: /cross/lib/libc.so.6: version `GLIBC_2.3' not found
(required by /cross/lib/libxerces-c.so)
libpthread.so.0 => /cross/lib/libpthread.so.0 (0x00cb3000)
libstdc++-libc6.2-2.so.3 => /cross/lib/libstdc++-libc6.2-2.so.3
(0x00f9d000)
libm.so.6 => /cross/lib/libm.so.6 (0x00111000)
libc.so.6 => /cross/lib/libc.so.6 (0x00132000)
/cross/lib/ld-linux.so.2 => /cross/lib/ld-linux.so.2 (0x00448000)
So how can I prevent that to happen?
It clearly seems to be a build problem or does xerces really need glibc2.3?
And if so, why didn't stop the build then?
Any ideas?
Greetings...
Stephan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBNym2bv5p9h9J588RAq3JAJ9pUK3XVhMXdfFK/4f6dmCK1b/HPQCghLqX
SJ9nnluU6yd6q1Zzmkq1+WE=
=ucIV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
