It's been rumoured that Rob Browning said:
> If I understand the problem right, I think Debian may have resolved
> this by making it policy to do a linking trick on all libraries that
> embeds the library dependency info into the shared library, so that
> you don't need to specify it on the compile line, but I'm not sure
> about that. In any case, on my system, I get libreadline libm and
> libdl automatically, even if I just specify -lguile -lqthreads on the
> link line...
Cool feature ...
> $ ldd /usr/lib/libguile.so.4
> /lib/nfslock.so.0 => /lib/nfslock.so.0 (0x4006d000)
> libdl.so.2 => /lib/libdl.so.2 (0x4007b000)
> libreadline.so.2 => /lib/libreadline.so.2 (0x4007f000)
> libm.so.6 => /lib/libm.so.6 (0x400aa000)
> libc.so.6 => /lib/libc.so.6 (0x400c2000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
> libncurses.so.4 => /lib/libncurses.so.4 (0x40164000)
Hmm .. my
ldd --version
ldd (GNU libc) 2.0.7
does this:
ldd /usr/lib/libguile.so.3.0.0
statically linked
even though I have to explicitly specify libdl libreadline and libm
to link.
When I do run ldd a.out, I notice that it automatically pulled
in libtermcap (how about that !!) even though I didn't specify it.
Wild, eh?
Oh, and gnucash works fine with /usr/lib/libguile.so.3.0.0 What's
libguile.so.4 ? aren't version numbers a pisser?
--linas
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
