From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: meson build issue
Date: Thu, 04 Jul 2019 17:08:36 +0100 [thread overview]
Message-ID: <65bb7b77d079ad43d301ee89d6d131d50c7cb686.camel@debian.org> (raw)
In-Reply-To: <20190704151747.GD439@bricha3-MOBL.ger.corp.intel.com>
On Thu, 2019-07-04 at 16:17 +0100, Bruce Richardson wrote:
> On Thu, Jul 04, 2019 at 04:44:48PM +0200, Thomas Monjalon wrote:
> > 04/07/2019 16:20, Bruce Richardson:
> > > On Thu, Jul 04, 2019 at 02:18:28PM +0000, Jerin Jacob
> > > Kollanukkaran wrote:
> > > > After inspecting the PATH. Its found that archlinux has very
> > > > latest pkgconf(1.6.1).
> > > > Pkgconf was overridden by a armv7 cross compile toolchain from
> > > > linaro.
> > > >
> > >
> > > Ok, thanks for the explanation. All working ok once that is
> > > fixed, I
> > > assume?
> >
> > What about RHEL 7.6 ?
> >
>
> No idea. However, this flag that caused problems is only needed for
> running
> the test script, it doesn't affect normal build and install.
>
> /Bruce
As far as I can see CentOS 7.6 has pkg-config 0.27.1 which is even
older (and no sign of pkgconf), so it won't work there either.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-07-04 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 13:57 [dpdk-dev] " Jerin Jacob Kollanukkaran
2019-07-04 14:01 ` Bruce Richardson
2019-07-04 14:14 ` Luca Boccassi
2019-07-04 14:18 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-07-04 14:20 ` Bruce Richardson
2019-07-04 14:44 ` Thomas Monjalon
2019-07-04 15:17 ` Bruce Richardson
2019-07-04 16:08 ` Luca Boccassi [this message]
2019-07-04 15:04 ` Jerin Jacob Kollanukkaran
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=65bb7b77d079ad43d301ee89d6d131d50c7cb686.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).