From: Cody Doucette <doucette@bu.edu>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, Cody Doucette <doucette@bu.edu>
Subject: [dpdk-dev] [PATCH v4 1/3] net/failsafe: remove D_XOPEN_SOURCE flag
Date: Wed, 31 Oct 2018 00:11:09 +0000 [thread overview]
Message-ID: <20181031001113.149469-2-doucette@bu.edu> (raw)
In-Reply-To: <20181031001113.149469-1-doucette@bu.edu>
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>
---
drivers/net/failsafe/Makefile | 1 -
drivers/net/failsafe/meson.build | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/net/failsafe/Makefile b/drivers/net/failsafe/Makefile
index 81802d092..eb9292425 100644
--- a/drivers/net/failsafe/Makefile
+++ b/drivers/net/failsafe/Makefile
@@ -34,7 +34,6 @@ CFLAGS += -std=gnu99 -Wextra
CFLAGS += -O3
CFLAGS += -I.
CFLAGS += -D_DEFAULT_SOURCE
-CFLAGS += -D_XOPEN_SOURCE=700
CFLAGS += $(WERROR_FLAGS)
CFLAGS += -Wno-strict-prototypes
CFLAGS += -pedantic
diff --git a/drivers/net/failsafe/meson.build b/drivers/net/failsafe/meson.build
index a249ff4af..d47a52acd 100644
--- a/drivers/net/failsafe/meson.build
+++ b/drivers/net/failsafe/meson.build
@@ -3,7 +3,6 @@
cflags += '-std=gnu99'
cflags += '-D_DEFAULT_SOURCE'
-cflags += '-D_XOPEN_SOURCE=700'
cflags += '-pedantic'
if host_machine.system() == 'linux'
cflags += '-DLINUX'
--
2.17.1
next prev parent reply other threads:[~2018-10-31 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 0:11 [dpdk-dev] [PATCH v4 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-10-31 0:11 ` Cody Doucette [this message]
2018-10-31 0:11 ` [dpdk-dev] [PATCH v4 2/3] net: add IPv6 extension header definitions Cody Doucette
2018-10-31 0:11 ` [dpdk-dev] [PATCH v4 3/3] ip_frag: extend IPv6 extension header parsing Cody Doucette
2018-10-31 0:15 ` Cody Doucette
2018-10-31 0:11 ` [dpdk-dev] [PATCH v4 3/3] ip_frag: extend IPv6 fragment header retrieval 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=20181031001113.149469-2-doucette@bu.edu \
--to=doucette@bu.edu \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.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).