DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] build break on BSD
Date: Thu, 17 Apr 2014 10:21:14 +0200	[thread overview]
Message-ID: <534F8EFA.4060208@6wind.com> (raw)
In-Reply-To: <20140416195220.GA2200@hmsreliant.think-freely.org>

Hi Neil,

On 04/16/2014 09:52 PM, Neil Horman wrote:
>      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);
>       ^
> [...]
>
> Looks like the recent whitelist/blacklist patches forgot to add the rte_devargs
> headers to the BSD build.

Thanks for reporting, I'll have a look ASAP.

Regards,
Olivier

      reply	other threads:[~2014-04-17  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 19:52 Neil Horman
2014-04-17  8:21 ` Olivier MATZ [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=534F8EFA.4060208@6wind.com \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).