From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Stokes, Ian" <ian.stokes@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Building DPDK Libraries with Libtool
Date: Thu, 03 Jul 2014 11:05:24 +0200 [thread overview]
Message-ID: <2199944.9mvWnhcZjY@xps13> (raw)
In-Reply-To: <CD7C01071941AC429549C17338DB8A52697509BB@IRSMSX101.ger.corp.intel.com>
Hi,
2014-07-03 08:30, Stokes, Ian:
> I have been using DPDK with Openvswitch. The latest release of Openvswitch
> has started to use Libtools to build it's own internal libraries. Previous
> to this I built DPDK using DPDKs Makefiles and linked against the required
> DPDK libraries in the Openvswitch Makefiles. However because of the
> Libtools change over we now receive the warnings like the following
>
> *** Warning: Linking the shared library lib/libopenvswitch.la against the
> *** static library
> /home/tester/rte/x86_64-ivshmem-linuxapp-gcc/lib/librte_mbuf.a is not
> portable!
You can build some shared libraries instead of static ones.
> For all the DPDK libraries we link against. Doing some research on this
> warning leads me to believe it is related to how Libtool interacts with
> static libraries that it has not built and the recommended solution seems
> to be use Libtool to build those libraries as well (In this case the DPDK
> libraries). Ideally I'd like to avoid this.
We should generate pkgconfig files in order to be easily integrated in libtool
applications.
PS: please remove the disclaimer in your email footer.
--
Thomas
prev parent reply other threads:[~2014-07-03 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 8:30 Stokes, Ian
2014-07-03 9:05 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2199944.9mvWnhcZjY@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).