From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] virtio UIO / PMD issues in default Ubuntu Cloud Images
Date: Tue, 14 Oct 2014 08:22:56 +0000 [thread overview]
Message-ID: <91383E96CE459D47BCE92EFBF5CE73B0C7E467@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20141014063406.GA17242@mhcomputing.net>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matthew Hall
> Sent: Tuesday, October 14, 2014 7:34 AM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] virtio UIO / PMD issues in default Ubuntu Cloud
> Images
>
>
>
> On Mon, Oct 13, 2014 at 11:03:53PM -0700, Matthew Hall wrote:
> > Another weird issue... when I tried to compile a DPDK shared lib using
> > clang I got this really, really weird error:
> >
> > /usr/bin/ld: test: hidden symbol `mknod' in
> > /usr/lib/x86_64-linux-gnu/libc_nonshared.a(mknod.oS) is referenced by
> > DSO
> > /usr/bin/ld: final link failed: Bad value
>
> Note: this specific error seems to be a bug in the behavior of DPDK
> compilation when the following two options are enabled simultaneously:
>
> CONFIG_RTE_BUILD_SHARED_LIB=y
> CONFIG_RTE_BUILD_COMBINE_LIBS=y
>
Hi Matthew,
The problem as you point out is that the combined library is not being linked properly,
in this case we are not linking against libc when building the shared library.
One way of fixing this issue is to use CC instead of LD to do the linking.
I have submitted a patch that updates the lib building process which main purpose was
to fix this issue but it seems that the removing of CONFIG_RTE_BUILD_COMBINE_LIBS
took over its real purpose.
Another fix that the patch fixes is linking against other external required libs
(ie. libm, librt, etc) when needed, so they would show on ldd if they are required.
Please have a look at http://dpdk.org/ml/archives/dev/2014-October/006453.html.
I would expect many of your issues to be fixed with that patch and would really
appreciate any feedback on it.
Thanks,
Sergio
> I think this is a pretty serious problem for anybody that's packaging or
> distributing a complete DPDK because compiling both the static and dynamic
> DPDK's at the same time as one another is going to fail with this weird error.
>
> Matthew.
next prev parent reply other threads:[~2014-10-14 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 5:45 Matthew Hall
2014-10-14 6:03 ` Matthew Hall
2014-10-14 6:34 ` Matthew Hall
2014-10-14 8:22 ` Gonzalez Monroy, Sergio [this message]
2014-10-14 8:34 ` Matthew Hall
2014-10-14 12:16 ` Gonzalez Monroy, Sergio
2014-10-17 8:56 ` Matthew Hall
2014-10-21 13:22 ` Gonzalez Monroy, Sergio
2014-10-22 7:17 ` Matthew Hall
2014-10-22 15:20 ` Gonzalez Monroy, Sergio
2014-10-22 18:41 ` Matthew Hall
2014-10-23 16:15 ` Gonzalez Monroy, Sergio
2014-10-14 6:43 ` Matthew Hall
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=91383E96CE459D47BCE92EFBF5CE73B0C7E467@IRSMSX108.ger.corp.intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).