From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] fix compilation on FreeBSD
Date: Fri, 27 Apr 2018 04:43:40 +0200 [thread overview]
Message-ID: <20180427024342.24054-1-thomas@monjalon.net> (raw)
The compilation was broken on FreeBSD due to the commit
for auxv, implemented only for Linux in the common files.
Thomas Monjalon (2):
eal: fix build with glibc < 2.16
eal: fix build on FreeBSD
lib/librte_eal/bsdapp/eal/Makefile | 1 +
lib/librte_eal/bsdapp/eal/eal_cpuflags.c | 21 ++++++
lib/librte_eal/bsdapp/eal/meson.build | 1 +
lib/librte_eal/common/eal_common_cpuflags.c | 79 ----------------------
lib/librte_eal/linuxapp/eal/Makefile | 1 +
.../eal/eal_cpuflags.c} | 49 +-------------
lib/librte_eal/linuxapp/eal/meson.build | 1 +
7 files changed, 27 insertions(+), 126 deletions(-)
create mode 100644 lib/librte_eal/bsdapp/eal/eal_cpuflags.c
copy lib/librte_eal/{common/eal_common_cpuflags.c => linuxapp/eal/eal_cpuflags.c} (60%)
--
2.16.2
next reply other threads:[~2018-04-27 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 2:43 Thomas Monjalon [this message]
2018-04-27 2:43 ` [dpdk-dev] [PATCH 1/2] eal: fix build with glibc < 2.16 Thomas Monjalon
2018-04-30 13:13 ` Aaron Conole
2018-04-27 2:43 ` [dpdk-dev] [PATCH 2/2] eal: fix build on FreeBSD Thomas Monjalon
2018-04-30 13:17 ` Aaron Conole
2018-04-27 9:03 ` [dpdk-dev] [PATCH 0/2] fix compilation " Maxime Coquelin
2018-04-27 9:16 ` 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=20180427024342.24054-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--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).