/usr/pkg/lib in default linker path

From:

Matthias Rampke <matthias@xxxxxxxxx>

Date:

Wed, 11 May 2011 13:27:57 +0200

Hello,
a problem has surfaced with some pkgsrc packages being confused by /usr/pkg/lib being in the default linker path - the configure scripts find that -l<library> works and thus conclude that they should use it, but fail at including the header because that's hidden by the pkgsrc wrappers (and rightly so, if there is no specified dependency that shouldn't happen).
This was introduced with the binutils 2.2.1 update. (Why?)
I've filed a PR concerning this[1] with pkgsrc as the "optimal" course to take is not immediately clear. As laid out there the options are:
1) no fix, broken packages will be fixed as they come up (i.e. "the bug is in the configure script")
2) fix in DragonFly, conforming to "expected" linker behaviour (aka. "you shouldn't do that") - swildner made a patch for this[2].
3) fix in pkgsrc generally. Unclear if possible at all, probably not without extending the linker with a "negative -L".
Any opinions?
-matthiasr
[1] http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=44953
[2] http://yoyodyne.ath.cx/tmp/lib_path.diff