From: "Stokes, Ian" <ian.stokes@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Building DPDK Libraries with Libtool
Date: Thu, 3 Jul 2014 08:30:41 +0000 [thread overview]
Message-ID: <CD7C01071941AC429549C17338DB8A52697509BB@IRSMSX101.ger.corp.intel.com> (raw)
Hi,
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!
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.
Has anyone linked DPDK static libraries to libtool libraries before and if so was it a case that DPDK had to be built with Libtool?
Regards
Ian
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
next reply other threads:[~2014-07-03 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 8:30 Stokes, Ian [this message]
2014-07-03 9:05 ` Thomas Monjalon
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=CD7C01071941AC429549C17338DB8A52697509BB@IRSMSX101.ger.corp.intel.com \
--to=ian.stokes@intel.com \
--cc=dev@dpdk.org \
/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).