From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 2EB9958EB for ; Fri, 2 May 2014 13:09:28 +0200 (CEST) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1WgBLM-00048B-G1; Fri, 02 May 2014 07:09:31 -0400 Date: Fri, 2 May 2014 07:09:27 -0400 From: Neil Horman To: Thomas Monjalon Message-ID: <20140502110927.GA15335@hmsreliant.think-freely.org> References: <1397585169-14537-2-git-send-email-nhorman@tuxdriver.com> <1397656304-468-1-git-send-email-nhorman@tuxdriver.com> <4041301.VqGVgh9vVV@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4041301.VqGVgh9vVV@xps13> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 01/15 v2] makefiles: Fixed -share command line option error 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: Fri, 02 May 2014 11:09:28 -0000 On Wed, Apr 30, 2014 at 01:42:12AM +0200, Thomas Monjalon wrote: > 2014-04-16 09:51, Neil Horman: > > The shared libraries built with the current makefile set produce static > > libraries rather than actual shared objects. This is due to several missing > > options that are required to correctly build shared objects using ld, as > > well as a mis-specified -share option (which should be -shared). Switching > > to the use of CC rather than LD and fixing the -shared option corrects > > these problems and builds the DSOs correctly. > > > > Signed-off-by: Neil Horman > > Applied for version 1.6.0r2. > > Thanks > -- > Thomas > So, I just went and looked at 1.6.0r2 and noted that you applied this patch, but the rest of the series is still missing. This is what I was talking about earlier when I said you weren't applying patch series atomically. It makes it impossible to have any clue what the upstream development head is going to look like. On top of that, since you're clearly integrating other changes ahead of this, theres every likelyhood the rest of my v5 series won't apply. the v5 series has sat out here for a few weeks now without comment. If there aren't any objections to it, apply it. Whats the problem here? I'm not going to package the DPDK until this series (or the functionality it offers) is in place. Neil