From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 697576A80 for ; Tue, 14 Oct 2014 10:27:28 +0200 (CEST) Received: from android-fb5fc4f6ed62fb42.attlocal.net (99-34-229-174.lightspeed.sntcca.sbcglobal.net [99.34.229.174]) by mail.mhcomputing.net (Postfix) with ESMTPSA id 78E5680C3D9; Tue, 14 Oct 2014 01:34:22 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B0C7E467@IRSMSX108.ger.corp.intel.com> References: <20141014054523.GA16919@mhcomputing.net> <20141014060353.GA17053@mhcomputing.net> <20141014063406.GA17242@mhcomputing.net> <91383E96CE459D47BCE92EFBF5CE73B0C7E467@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Matthew Hall Date: Tue, 14 Oct 2014 01:34:50 -0700 To: "Gonzalez Monroy, Sergio" , "dev@dpdk.org" Message-ID: <3CCF4B14-58A7-4499-98A1-8D617A6F86B7@mhcomputing.net> Subject: Re: [dpdk-dev] virtio UIO / PMD issues in default Ubuntu Cloud Images X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 08:27:28 -0000 Yes, I suspected some of your patches were related to this besides just the COMBINE_LIBS options. However none of these will fix the issue that the virtio non-UIO PMD doesn't work right with a statically linked DPDK, so, despite all your fixes I've still got problems getting it all to work right. Matthew. -- Sent from my mobile device. On October 14, 2014 1:22:56 AM PDT, "Gonzalez Monroy, Sergio" wrote: > > >> -----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.