Re: use of libtool for linking executables - rpath problem

[Jan D.]

In article <address@hidden>,
Russ Allbery <address@hidden> wrote:
> Rob Browning <address@hidden> writes:

> > The problem I'm talking about is if Makefile.am's use
> 
> >   LDFLAGS = `gnome-config --libs foo` `foo-config --libs bar`
> 
> > then if you've got a normal gnome-dev package installed, such that
> > it's libs are in /usr/lib, it will (or at least it used to) put
> > -L/usr/lib into LDFLAGS ahead of whatever foo-config specifies.

> This is a bug in the packaging that should be reported to your
> distribution.  Under no circumstances should /usr/lib, /usr/include, and
> other such default paths be included in the configured link or compile
> flags, and the packager needs to fix them if they are.

Just some datapoints.  Of the 35 packages gnome-config on my system
knows about, 29 had -L/usr/lib and 28 -I/usr/include.

This makes it very hard to try out versions that also are in /usr/lib,
/usr/include.

It seems to me that gnome-config and friends are made for a steady state
system.

        Jan D.