Re: [Xen-devel] [PATCH 1 of 5 V2] remus: add libnl3 dependency to autoconf scripts

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2013-10-09 at 09:27 -0700, Shriram Rajagopalan wrote:

> The issue with libnl3 is "compiling" - i.e., dev headers, that libxl
> uses to invoke libnl API.

This is what pkg-config describes. pkg-config is about compiling and
linking, not runtime dependencies as you seem to be thinking.

> There is no pkg-config module for libnl3 development headers (Just
> like the ones for 
> libraries: libnl-3.0, libnl-route-3.0, etc) [see
> http://git.infradead.org/users/tgr/libnl.git/tree ]

> It has package config files for libnl-3.0.pc (-lnl-3),
> libnl-route-3.0.pc (-lnl-route-3)
> but none for dev headers.

The .pc is *part of* the dev headers, not the runtime library7.

> Do they get installed along with the libraries ? Don't think so
> (atleast on debian & ubuntu).

The .pc file is in the -dev package, alongside the headers. This is hte
pkg-config model.
        $ dpkg -L libnl-3-dev | grep \.pc
        /usr/lib/x86_64-linux-gnu/pkgconfig/libnl-3.0.pc
        
If pkg-config says libnl-3 exists to be compiled/linked against then by
definition the headers must be present.

Or are you trying to say that libnl3 is somehow a different thing to
libnl-3.0?

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel