From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Compile errors with libc < 2.12 Date: Wed, 18 Nov 2015 15:24:56 +0100 Message-ID: <103431910.iACTIb73WP@xps13> References: <20151118133220.GA11599@sivlogin002.ir.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Ferruh Yigit Return-path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id 8D0EF3777 for ; Wed, 18 Nov 2015 15:26:10 +0100 (CET) Received: by wmdw130 with SMTP id w130so200846327wmd.0 for ; Wed, 18 Nov 2015 06:26:10 -0800 (PST) In-Reply-To: <20151118133220.GA11599@sivlogin002.ir.intel.com> 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" 2015-11-18 13:32, Ferruh Yigit: > When libc version is < 2.12 there are two compile errors, both introduced in DPDK2.2, more details below. > > We can solve issue in a few ways: > 1- Ignore errors, this depends on if any user has this version. glibc 2.12 released around 2010, still may have distros with libc < 2.12, at least SUSE11 does. > 2- Make DPDK compatible with older glibc versions. > 3- Use a compile option to wrap functionality that fails > > I prefer option 2, > option 1 may break DPDK for some users, and option 3 adds new complexity and dependency to maintain. > > Please advise how to proceed? Yes, please try the option 2. Having a degraded mode for old libc is acceptable. So you can use some stubs. Thanks