From: Bruce Richardson <bruce.richardson@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] mlx: fix compilation with Glibc 2.20
Date: Mon, 20 Jun 2016 16:24:50 +0100 [thread overview]
Message-ID: <20160620152449.GA17588@bricha3-MOBL3> (raw)
In-Reply-To: <1466429506-16922-1-git-send-email-adrien.mazarguil@6wind.com>
On Mon, Jun 20, 2016 at 03:31:46PM +0200, Adrien Mazarguil wrote:
> Since _BSD_SOURCE was deprecated in favor of _DEFAULT_SOURCE in Glibc 2.19
> and entirely removed in 2.20, various BSD ioctl macros are not exposed
> anymore when _XOPEN_SOURCE is defined, and linux/if.h now conflicts with
> net/if.h.
>
> Add _DEFAULT_SOURCE and keep _BSD_SOURCE for compatibility with older
> versions.
>
> Suggested-by: Bruce Richardson <bruce.richardson@intel.com>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Applied to dpdk-next-net in place of previous incomplete fix.
/Bruce
prev parent reply other threads:[~2016-06-20 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 15:09 [dpdk-dev] [PATCH 1/2] mlx: fix compilation with recent Glibc Adrien Mazarguil
2016-06-10 15:09 ` [dpdk-dev] [PATCH 2/2] mlx: regenerate autoconf file automatically Adrien Mazarguil
2016-06-13 12:53 ` [dpdk-dev] [PATCH 1/2] mlx: fix compilation with recent Glibc Bruce Richardson
2016-06-13 13:08 ` Bruce Richardson
2016-06-14 9:22 ` [dpdk-dev] [PATCH] mlx: fix compilation with older Glibc Adrien Mazarguil
2016-06-17 16:29 ` Ferruh Yigit
2016-06-20 9:25 ` Adrien Mazarguil
2016-06-20 10:04 ` Bruce Richardson
2016-06-20 13:31 ` [dpdk-dev] [PATCH v2] mlx: fix compilation with Glibc 2.20 Adrien Mazarguil
2016-06-20 15:24 ` Bruce Richardson [this message]
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=20160620152449.GA17588@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).