cvs commit: src/contrib/gcc/config freebsd-spec.h

Ruslan Ermilov ru at
Tue Sep 2 08:57:30 PDT 2003

> On Tue, 2 Sep 2003, Robert Watson wrote:
> > The effect I'm most interested in "getting right" at this point has to do
> > with library dependencies in third party applications.  Right now, when we
> > build QT on FreeBSD, the resulting library has an explicit dependency on
> > libc_r:
> > 
> > paprika# ldd /usr/X11R6/lib/
> > /usr/X11R6/lib/
> > => /usr/local/lib/ (0x287bc000)
> > ...
> > => /usr/lib/ (0x28b06000)
> > ...
> > 
> > On my notebook, I use libmapl.conf to rewrite the dependency such that KSE
> > is used.  I think it's very important that we avoid a situation where, if
> > there are potential future changes in threading libraries, we find
> > binaries dependent on various threading libraries.  I'd like to see a
> > dependency on a single name, with a way to substitute that name.  I.e.,
> > all libraries dependent on a threading library, unless explicitly
> > configured otherwise, should be linked against a single common library.
> > 
> > Otherwise, if we wipe out libc_r someday, or remove the 1:1 version of KDE
> > and decide M:N is the one true way, we'll leave users up a creek.

If the idea is to always have binaries internally linked to one name,
that could be tricky.  The problem is that linker takes an internal
name of the library from the library's binary, so if you link against
-lfoo, and /usr/lib/ -> /usr/lib/, is what will
be written into a binary.  We've been through this already with
libtermcap -> libncurses.

Ruslan Ermilov		Sysadmin and DBA,
ru at		Sunbay Software Ltd,
ru at		FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the cvs-src mailing list