From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2] mk: fix ABI versioning compile error for combined shared library Date: Mon, 2 Nov 2015 19:18:45 +0000 Message-ID: <20151102191845.GA22056@sivlogin002.ir.intel.com> References: <20151102102023.GA29052@sivlogin002.ir.intel.com> <1446477827-11541-1-git-send-email-ferruh.yigit@intel.com> <2999923.OMi2XSDyte@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, Eric Kinzie To: Thomas Monjalon Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 294948D99 for ; Mon, 2 Nov 2015 20:18:52 +0100 (CET) Content-Disposition: inline In-Reply-To: <2999923.OMi2XSDyte@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Nov 02, 2015 at 05:26:21PM +0100, Thomas Monjalon wrote: > 2015-11-02 15:23, Ferruh Yigit: > > +ifeq ($(COMBINED_BUILD),1) > > include $(RTE_SDK)/mk/rte.sharelib.mk > > +endif > > Why this ifeq? > rte.sharelib.mk is always used for combined lib. > When combine lib config selected, other libraries still build And all libraris include sharelib.mk This cause CPU_LDFLAGS conflict, the CPU_LDFLAGS set specially for combined lib used by all libraries. When not linking combined library, there is no need/benefit of including sharelib.mk COMBINED_BUILD only set when linking combined library and that is when sharelib.mk included I can try to prevent linking other libraries when combined library enabled, then sharelib.mk included only for combined lib, and we can remove that check. But I am not sure how hard it is, and does it worth spending extra effort to it? Thanks, ferruh