DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
	 Anand Rawat <anand.rawat@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: remove exec-env directory
Date: Tue, 2 Apr 2019 22:04:46 +0200	[thread overview]
Message-ID: <CAJFAV8yHfCdufB8mb_-F4JuV4yp63nA6mNTPm6OY97yoWk3Ocw@mail.gmail.com> (raw)
Message-ID: <20190402200446.GipupkdwI2r6dtCASQ3NPyZ7PKkF1pQpdukhqvCRTmo@z> (raw)
In-Reply-To: <6c52aa71-5dcb-1dfe-27f3-57d11dcb5a2f@intel.com>

On Tue, Apr 2, 2019 at 9:58 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 4/2/2019 8:55 PM, David Marchand wrote:
> > On Tue, Apr 2, 2019 at 9:52 PM Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
> >> On 4/2/2019 8:46 PM, David Marchand wrote:
> >>> Bruce, while testing with meson, I noticed this:
> >>> kernel/linux/kni/meson.build:16: WARNING: Passed invalid keyword
> argument
> >>> "console".
> >>> WARNING: This will become a hard error in the future.
> >>> WARNING: Unknown keyword arguments in target rte_kni: console
> >>
> >> I am not seeing this...
> >>
> >
> > Ok, might be my setup:
> > [dmarchan@dmarchan dpdk]$ meson --version
> > 0.47.2
> >
> > What should I check ?
>
> I have '0.50.0', but no idea what to check, wait Bruce :) ?
>

Looking at the doc..
3 ``pip`` tool, e.g. ``pip3 install meson``. Version 0.42 of meson is
recommended - if the version packaged is too old, the latest version is
generally available from "pip".

Later:
NOTE: for --static builds, DPDK needs to be built with Meson >= 0.46 in
order to
fully generate the list of private dependencies. If DPDK is built with an
older
version of Meson, it might be necessary to manually specify dependencies of
DPDK
PMDs/libraries, for example -lmlx5 -lmnl for librte-pmd-mlx5, or the static
link
step might fail.

And I found this:
meson.build:    meson_version: '>= 0.47.1'

So I suppose I have a working environment and I will just ignore the
warnings :-)

-- 
David Marchand

  parent reply	other threads:[~2019-04-02 20:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 23:07 [dpdk-dev] [PATCH] " Thomas Monjalon
2019-04-01 23:07 ` Thomas Monjalon
2019-04-02  9:39 ` Bruce Richardson
2019-04-02  9:39   ` Bruce Richardson
2019-04-02 14:43   ` Ferruh Yigit
2019-04-02 14:43     ` Ferruh Yigit
2019-04-02  9:57 ` David Marchand
2019-04-02  9:57   ` David Marchand
2019-04-02 10:03   ` Thomas Monjalon
2019-04-02 10:03     ` Thomas Monjalon
2019-04-02 15:13 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-04-02 15:13   ` Thomas Monjalon
2019-04-02 19:30 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2019-04-02 19:30   ` Thomas Monjalon
2019-04-02 19:46   ` David Marchand
2019-04-02 19:46     ` David Marchand
2019-04-02 19:50     ` Thomas Monjalon
2019-04-02 19:50       ` Thomas Monjalon
2019-04-03  8:41       ` David Marchand
2019-04-03  8:41         ` David Marchand
2019-04-02 19:52     ` Ferruh Yigit
2019-04-02 19:52       ` Ferruh Yigit
2019-04-02 19:55       ` David Marchand
2019-04-02 19:55         ` David Marchand
2019-04-02 19:57         ` Ferruh Yigit
2019-04-02 19:57           ` Ferruh Yigit
2019-04-02 20:04           ` David Marchand [this message]
2019-04-02 20:04             ` David Marchand
2019-04-02 20:09             ` Thomas Monjalon
2019-04-02 20:09               ` Thomas Monjalon
2019-04-03 13:34       ` Bruce Richardson
2019-04-03 13:34         ` Bruce Richardson
2019-04-02 19:50   ` Ferruh Yigit
2019-04-02 19:50     ` Ferruh Yigit

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=CAJFAV8yHfCdufB8mb_-F4JuV4yp63nA6mNTPm6OY97yoWk3Ocw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=anand.rawat@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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).