[Pkg-dpdk-devel] not-so-multiarch

Christian Ehrhardt christian.ehrhardt at canonical.com
Wed Jul 5 09:24:50 UTC 2017

On Wed, Jul 5, 2017 at 10:59 AM, Luca Boccassi <luca.boccassi at gmail.com>

> Just a note regarding the libs: if DPDK_LIBS is not used, how does it get
> the list of libraries to link to?

It searches for -llibdpdk which will trigger the linker script generating
the group of linking arguments.

> Check if there's a LIBS variable, might be a better one to append to
> rather than LDFLAGS (it's also correct, the latter is for linker flags, not
> for libs).

While that seems true to me as well I'd prefer to only change what we can
explain we need it for.
In that case changing libs is not required so it would add complexity to
the change that is going to be discussed.
But please feel free to suggest there.

> Regarding fetching variables from pkgconfig it can be done in autoconf,
> I'll find how and forward it.

Ok, in case we want/need to add those to libs that would be my way to go.
Yet OTOH the linker script only adds the group and not the -lz and others
that the libs in pkg-config do.

Not consuming projects for all the linking issues dpdk had in the past
sometimes mess with that - in the openvswitch case, they put all in a
-whole statement.
That ensures that all libs are linked, but since our pkg-config list is
more complete (longer) than the lindpdk linker script it might change
things in an unwanted way.
Another reason to not change the usage of libs unless needed I'd think.

I just submitted to openvswitch development and set you on CC.
Lets discuss there on the proposed change as needed - you might also be
able to help answering some questions that might come up.

Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-dpdk-devel/attachments/20170705/b8de5b3f/attachment.html>

More information about the Pkg-dpdk-devel mailing list