Re: [Bug-gnubg] Compile & crash on Solaris

[Holger]

Hi Joern and Jim (and potential readers of this thread),

sorry to have left you hanging until now. I didn't make it to the CS faculty
earlier today.
Thanks a lot to both of you for your tips and comments so far.

Jim Segrave wrote:
> Holger wrote:
> > ld.so.1: ./bin/gnubg: fatal: relocation error: file ./bin/gnubg: symbol
> > xmlCatalogResolve: referenced symbol not found
> > Killed
>
> It looks like you have an odd/too-old version of libxml.

The problem is that there are several. You'd probably shout Hurray if you'd
see this system.

fiesta (~): echo
$LD_LIBRARY_PATH
/usr/lib:/usr/local/lib:/usr/KDE/2/lib:/usr/gnome/2.0/lib:/usr/gnome/lib:/etc/lib:/usr/4lib:/home/pub/lib
fiesta (~): find `echo $LD_LIBRARY_PATH | sed -e 'y/:/ /'` -name '*libxml*'
-print | & grep -v -e find: | more
/usr/KDE/2/lib/libxml2.so.2
/usr/KDE/2/lib/libxml2.so.2.4.1
/usr/KDE/2/lib/libxml2.so
/usr/KDE/2/lib/pkgconfig/libxml-2.0.pc
/usr/KDE/2/lib/libxml2.la
/usr/KDE/2/lib/libxml2.a
/usr/gnome/2.0/lib/pkgconfig/libxml-2.0.pc
/usr/gnome/2.0/lib/libxml2.la
/usr/gnome/2.0/lib/libxml2.so
/usr/gnome/2.0/lib/libxml2.so.2
/usr/gnome/2.0/lib/libxml2.so.2.4.22
/usr/gnome/lib/libxml.so.1
/usr/gnome/lib/libxml.so.1.8.10
/usr/gnome/lib/libxml.a
/usr/gnome/lib/libxml.la
/usr/gnome/lib/libxml.so
/home/pub/lib/mozilla-0.9.8/components/libxmlextras.so
/home/pub/lib/mozilla1.1/components/libxmlextras.so
/home/pub/lib/mozilla1.1/components/libxmlterm.so
/home/pub/lib/libxml2-2.4.30
/home/pub/lib/libxml2-2.4.30/include/libxml2
/home/pub/lib/libxml2-2.4.30/include/libxml2/libxml
/home/pub/lib/libxml2-2.4.30/lib/libxml2.so.2
/home/pub/lib/libxml2-2.4.30/lib/libxml2.so.2.4.30
/home/pub/lib/libxml2-2.4.30/lib/libxml2.so
/home/pub/lib/libxml2-2.4.30/lib/pkgconfig/libxml-2.0.pc
/home/pub/lib/libxml2-2.4.30/lib/libxml2.la
/home/pub/lib/libxml2-2.4.30/lib/libxml2.a
/home/pub/lib/libxml2-2.4.30/man/man3/libxml.3
/home/pub/lib/libxml2-2.4.30/share/aclocal/libxml.m4
/home/pub/lib/libxml2-2.4.30/share/doc/libxml2-2.4.30
/home/pub/lib/mozilla1.2/components/libxmlextras.so

Jim Segrave wrote:
> On Fri 03 Jan 2003 (10:01 +0000), Joern Thyssen wrote:
> > On Fri, Jan 03, 2003 at 10:43:07AM +0100, Jim Segrave wrote
> > > On Fri 03 Jan 2003 (07:59 +0000), Joern Thyssen wrote:
> > > >
> > > > It looks like an error message from the runtime dynamic library
> > > > resolver.
> > > >
> > > > Does Solaris actually link the gnubg executable without having
> > > > resolved all external references?
> > > >
> > > > Holger, did you compile it on the same machine as you're running it
> > > > from?

Yes.

> > > Since Holger is not root on this machine, and can't (I assume) install
> > > libraries in /usr/local/lib (or /opt/local/lib or wherever), there is

True. Only to /home/pub/... and home directories. The libxml2-2.4.30 is
"mine".

> > > a possibility that it's built to use a libxml of Holger's but at run
> > > time is using a system libxml which is older or less complete.
> > >
> > > ldd of gnubg may point to where it's going for libxml. You might need
> > > to set LDPATH or run ldconfig if my speculation above is correct.

Yesterday I had started to set up a lib folder in my home directory and make
symlinks to the lib versions I want to use and then put it up front in
LD_LIBRARY_PATH or sort. Unfortunately, the NFS server f***** up so that I could
only 'kill -9 -1' and go home. So now I'm going to try again.

Which variable(s) do I need to set? I've set LIBPATH and LD_LIBRARY_PATH.
What about LDPATH and maybe more? Which does what? And where do I specify the
matching include path?

> > Is it possible to run ldconfig as non-root?

Doesn't seem to exist. Does ldd do the same? .. Ah, seems so:

fiesta (~): ldd /home/pub/lib/gnubg-030102/bin/gnubg 
        libgtk-x11-2.0.so.0 =>   /usr/gnome/2.0/lib/libgtk-x11-2.0.so.0
        libgdk-x11-2.0.so.0 =>   /usr/gnome/2.0/lib/libgdk-x11-2.0.so.0
        libatk-1.0.so.0 =>       /usr/gnome/2.0/lib/libatk-1.0.so.0
        libgdk_pixbuf-2.0.so.0 =>       
/usr/gnome/2.0/lib/libgdk_pixbuf-2.0.so.0
        libm.so.1 =>     /usr/lib/libm.so.1
        libpangox-1.0.so.0 =>    /usr/gnome/2.0/lib/libpangox-1.0.so.0
        libpango-1.0.so.0 =>     /usr/gnome/2.0/lib/libpango-1.0.so.0
        libgobject-2.0.so.0 =>   /usr/gnome/2.0/lib/libgobject-2.0.so.0
        libgmodule-2.0.so.0 =>   /usr/gnome/2.0/lib/libgmodule-2.0.so.0
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libglib-2.0.so.0 =>      /usr/gnome/2.0/lib/libglib-2.0.so.0
-->     libxml2.so.2 =>  /usr/KDE/2/lib/libxml2.so.2
        libz.so =>       /usr/lib/libz.so
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libfreetype.so.6 =>      /usr/gnome/2.0/lib/libfreetype.so.6
        libresolv.so.2 =>        /usr/lib/libresolv.so.2
        libgdbm.so.1.7.3 =>      /usr/local/lib/libgdbm.so.1.7.3
        libreadline.so.4 =>      /usr/local/lib/libreadline.so.4
        libcurses.so.1 =>        /usr/lib/libcurses.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libX11.so.4 =>   /usr/lib/libX11.so.4
        libXext.so.0 =>  /usr/lib/libXext.so.0
        libgintl.so.1 =>         /usr/gnome/2.0/lib/libgintl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        libdga.so.1 =>   /usr/openwin/lib/libdga.so.1
        /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1

fiesta (~): l /usr/KDE/2/lib/libxml2.so.2
lrwxrwxrwx   1 binner         16 Aug 10  2001 /usr/KDE/2/lib/libxml2.so.2 ->
libxml2.so.2.4.1

> > On linux it's LD_LIBRARY_PATH.
> >
> > An alternative solution is to link libxml2 static cy changing -lxml2 to
> > /path/to/the/correct/libxml.a in the Makefile. There might be the same
> > problem with other libraries installed locally, e.g., libpng, which
> > could explain the error Holger reported regarding pnmto-something while
> > running make. Holger, you may have to set LDPATH/LD_LIBRARY_PATH before
> > running make to avoid the make-errors.

See above. I've always tried to figure out reasonable environment settings
for this system since I've got this account. Not the easiest task.

> > After succesful installation you can make a shell script wrapper for
> > gnubg:
> >
> > $ mv gnubg gnubg.x
> > $ cat > gnubg
> > #/bin/sh
> > export LD_LIBRARY_PATH=/path/to/the/correct/lib/directory
> > gnubg.x
> > ^D
> > $ chmod +x gnubg

OK. I'll try this with my lib directory.

> I just hope Holger remembers this is a guess at a possible cause of
> the problem. It may be totally unrelated (hence my suggestion of an
> ldd to see what gnubg will actually use for libs).

I do. But it seems to be likely the fault. Hence also my initial question
for the path settings.

I'll report on my progress in a while.

Regards, 

      Holger

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!