From: Neil Horman <nhorman@tuxdriver.com>
To: dev@dpdk.org
Subject: [dpdk-dev] build break on BSD
Date: Wed, 16 Apr 2014 15:52:20 -0400 [thread overview]
Message-ID: <20140416195220.GA2200@hmsreliant.think-freely.org> (raw)
Hey-
I was just trying to do a build on bsd for dpdk and hit this:
== Build lib/librte_eal/bsdapp/eal
CC eal.o
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c: In function ‘eal_parse_args’:
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:654:5: error: implicit
declaration of function ‘eal_dev_whitelist_add_entry’
[-Werror=implicit-function-declaration]
eal_dev_whitelist_add_entry(optarg);
^
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:654:5: error: nested extern
declaration of ‘eal_dev_whitelist_add_entry’ [-Werror=nested-externs]
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:715:3: error: implicit
declaration of function ‘eal_dev_whitelist_exists’
[-Werror=implicit-function-declaration]
if (eal_dev_whitelist_exists()) {
^
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:715:3: error: nested extern
declaration of ‘eal_dev_whitelist_exists’ [-Werror=nested-externs]
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:721:3: error: implicit
declaration of function ‘rte_eal_pci_set_blacklist’
[-Werror=implicit-function-declaration]
rte_eal_pci_set_blacklist(eal_dev_blacklist, blacklist_index);
^
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:721:3: error: nested extern
declaration of ‘rte_eal_pci_set_blacklist’ [-Werror=nested-externs]
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:723:3: error: implicit
declaration of function ‘eal_dev_whitelist_parse’
[-Werror=implicit-function-declaration]
if (eal_dev_whitelist_exists() && eal_dev_whitelist_parse() < 0) {
^
/root/git/dpdk/lib/librte_eal/bsdapp/eal/eal.c:723:3: error: nested extern
declaration of ‘eal_dev_whitelist_parse’ [-Werror=nested-externs]
Looks like the recent whitelist/blacklist patches forgot to add the rte_devargs
headers to the BSD build.
Neil
next reply other threads:[~2014-04-16 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 19:52 Neil Horman [this message]
2014-04-17 8:21 ` Olivier MATZ
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=20140416195220.GA2200@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.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).