So what is up with the "Requires.private" entries in various pkgconfig .pc files ? Most mock fc5 builds are currently failing because of a missing dependency between libX11-devel and libxau-devel. Culprit seems to be :
bash-3.00# grep -i requires /usr/lib/pkgconfig/x11.pc Requires: xproto kbproto inputproto Requires.private: xau xdmcp
On Sun, 2005-12-18 at 14:46 -0800, Denis Leroy wrote:
So what is up with the "Requires.private" entries in various pkgconfig .pc files ? Most mock fc5 builds are currently failing because of a missing dependency between libX11-devel and libxau-devel. Culprit seems to be :
bash-3.00# grep -i requires /usr/lib/pkgconfig/x11.pc Requires: xproto kbproto inputproto Requires.private: xau xdmcp
If A Requires.private: B, that means libA links to libB, but apps/libs that link to libA does not have to link to libB (when linking dynamically on platforms that support library dependencies, like Linux).
It should not affect -devel packages.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl@redhat.com alla@lysator.liu.se He's a sword-wielding Catholic farmboy searching for his wife's true killer. She's a wealthy hip-hop archaeologist fleeing from a Satanic cult. They fight crime!
Alexander Larsson wrote:
If A Requires.private: B, that means libA links to libB, but apps/libs that link to libA does not have to link to libB (when linking dynamically on platforms that support library dependencies, like Linux).
Very nice. Avoids library linking bloat. Too bad libtool archives don't include a "private" feature (at least, AFAIK they don't).
-- Rex
On Mon, 2005-12-19 at 07:04 -0600, Rex Dieter wrote:
Alexander Larsson wrote:
If A Requires.private: B, that means libA links to libB, but apps/libs that link to libA does not have to link to libB (when linking dynamically on platforms that support library dependencies, like Linux).
Very nice. Avoids library linking bloat. Too bad libtool archives don't include a "private" feature (at least, AFAIK they don't).`\
you can achieve the same by giving ld the -Wl,--as-needed flag, then ld will just drop unused linked-to libraries. Unfortunately libtool effectively filters this out as well ;(
On Mon, Dec 19, 2005 at 02:18:24PM +0100, Arjan van de Ven wrote:
you can achieve the same by giving ld the -Wl,--as-needed flag, then ld will just drop unused linked-to libraries. Unfortunately libtool effectively filters this out as well ;(
I have tried this for a BMP plugin I wrote (it links against all the libraries BMP links against, which is rather a lot), and --as-needed dropped far too much libraries, so I ended up with undefined symbols.
Alexander Larsson wrote:
If A Requires.private: B, that means libA links to libB, but apps/libs that link to libA does not have to link to libB (when linking dynamically on platforms that support library dependencies, like Linux).
Very nice. Avoids library linking bloat. Too bad libtool archives don't include a "private" feature (at least, AFAIK they don't).
-- Rex
-
Alexander Larsson -
Arjan van de Ven -
Denis Leroy -
Ralf Ertzinger -
Rex Dieter