From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, Cody Doucette <doucette@bu.edu>,
Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v5 1/3] net/failsafe: remove D_XOPEN_SOURCE flag
Date: Wed, 31 Oct 2018 18:02:29 +0100 [thread overview]
Message-ID: <1585740.4slmyqDWMi@xps> (raw)
In-Reply-To: <20181031021758.66752-2-doucette@bu.edu>
31/10/2018 03:17, Cody Doucette:
> Compilation flag D_XOPEN_SOURCE is causing failsafe to fail to
> build when changing some DPDK libraries. The flag is not needed
> and therefore is removed.
>
> Signed-off-by: Cody Doucette <doucette@bu.edu>
Gaetan, please approve that the flag is not needed.
next prev parent reply other threads:[~2018-10-31 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 2:17 [dpdk-dev] [PATCH v5 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 1/3] net/failsafe: remove D_XOPEN_SOURCE flag Cody Doucette
2018-10-31 17:02 ` Thomas Monjalon [this message]
2018-10-31 21:10 ` Gaëtan Rivet
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 2/3] net: add IPv6 extension header definitions Cody Doucette
2018-10-31 17:03 ` Thomas Monjalon
2018-11-05 8:45 ` Olivier Matz
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval Cody Doucette
2018-10-31 17:03 ` Thomas Monjalon
2018-10-31 19:56 ` Ananyev, Konstantin
2018-11-07 20:21 ` Cody Doucette
2018-11-07 23:00 ` Ananyev, Konstantin
2023-06-12 2:27 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2018-10-31 0:17 [dpdk-dev] [PATCH v4 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-10-31 0:17 ` [dpdk-dev] [PATCH v5 1/3] net/failsafe: remove D_XOPEN_SOURCE flag Cody Doucette
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=1585740.4slmyqDWMi@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=doucette@bu.edu \
--cc=gaetan.rivet@6wind.com \
--cc=matan@mellanox.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).