DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Compile errors with libc < 2.12
Date: Wed, 18 Nov 2015 13:32:20 +0000	[thread overview]
Message-ID: <20151118133220.GA11599@sivlogin002.ir.intel.com> (raw)

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? 



Compile issues:
1- pthread_setname_np() 
Error msg: error: implicit declaration of function ‘pthread_setname_np’
Reason: pthread_setname_np() introduced in glibc 2.12
Commit: eal: set name to threads (commit 67b6d3039e9edbc4624c878c6930be5e126e8b58)
Introduced in: DPDK2.2
Comment: This is mostly for debug, can be reverted without functionality loss


2- CLOCK_MONOTONIC_RAW macro
Error msg: error: identifier "CLOCK_MONOTONIC_RAW" is undefined
Reason: CLOCK_MONOTONIC_RAW introduced in glibc 2.12
Commit eal/linux: make alarm not affected by system time jump (commit d08d304508a8a8caf255baf622ab65db1fec952c)
Introduced in: DPDK2.2
Comment: Can keep functionality but may use supported "CLOCK_MONOTONIC" instead of "CLOCK_MONOTONIC_RAW"


Thanks,
ferruh

             reply	other threads:[~2015-11-18 13:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 13:32 Ferruh Yigit [this message]
2015-11-18 14:24 ` Thomas Monjalon
2015-11-19 11:22   ` [dpdk-dev] [PATCH] Revert "eal: set name to threads" Ferruh Yigit
2015-11-19 11:49     ` Panu Matilainen
2015-11-19 12:32       ` Thomas Monjalon
2015-11-19 13:39         ` Ferruh Yigit
2015-11-19 16:59           ` Ferruh Yigit
2015-11-19 17:44             ` [dpdk-dev] [PATCH] eal: fix compile error for old glibc caused by pthread_setname_np() Ferruh Yigit
2015-11-20 12:21               ` [dpdk-dev] [PATCH] eal: fix compile error for old glibc caused by pthread_setname_np()# Bruce Richardson
2015-11-24 14:26                 ` Ferruh Yigit
2015-11-24 17:54               ` [dpdk-dev] [PATCH] eal: fix compile error for old glibc caused by pthread_setname_np() Thomas Monjalon
2015-11-24 18:47                 ` Ferruh Yigit
2015-11-25 11:13                   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2015-11-25 11:18                     ` Thomas Monjalon
2015-11-25 11:24                       ` Ferruh Yigit
2015-11-25 11:30                         ` Thomas Monjalon
2015-11-25 13:41                     ` Thomas Monjalon
2015-11-25 13:51                     ` Roger B. Melton
2015-11-25 14:03                       ` Thomas Monjalon
2015-11-25 14:20                         ` Roger B. Melton
2015-11-19 11:23   ` [dpdk-dev] [PATCH] eal: fix compile error for old glibc caused by CLOCK_MONOTONIC_RAW Ferruh Yigit
2015-11-20 17:02     ` Thomas Monjalon

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=20151118133220.GA11599@sivlogin002.ir.intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    /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).