Scott Cantor <cantor.2 <at> osu.edu> writes:
>
> > I'm having some problems with running configure to build the binaries for
> > xmlsecurity. The conf.log file is attached. Can someone help sort out
> > these problems? It would be very much appreciated.
>
> Looks to me like you've got a Xerces-C 2.x that's built with Sun's compiler
> and then you're trying to build this with gcc. You can't mix them.
>
> There may also be library path issues causing trouble, but it looks more
> like a compiler mismatch to me.
>
> Run ldd against libxerces-c and see what it's linked to. libCrun would
> indicate Sun's and libstdc++ would be gcc.
>
Yes, you're right.
>ldd libxerces-c.so
libpthread.so.1 => /usr/lib/libpthread.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libc.so.1 => /usr/lib/libc.so.1
libmp.so.2 => /usr/lib/libmp.so.2
libthread.so.1 => /usr/lib/libthread.so.1
librt.so.1 => /usr/lib/librt.so.1
libaio.so.1 => /usr/lib/libaio.so.1
libmd5.so.1 => /usr/lib/libmd5.so.1
/usr/platform/SUNW,UltraAX-MP/lib/libc_psr.so.1
/usr/platform/SUNW,UltraAX-MP/lib/libmd5_psr.so.1
I'll retry running "configure" by setting the env var CC to point to Sun's C
compiler.
BTW, if the API binaries on nagoya.apache.org were accessible, it would make
my life a lot easier. Do you know what's wrong with this site?
Paul.
