From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Luca Boccassi <bluca@debian.org>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [EXT] Re: meson build issue
Date: Thu, 4 Jul 2019 14:18:28 +0000 [thread overview]
Message-ID: <BYAPR18MB2424FC02BD21C5FC3751B82CC8FA0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1f973d3fe747dded4163a7b850c93e6a220b4dea.camel@debian.org>
> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Thursday, July 4, 2019 7:45 PM
> To: Bruce Richardson <bruce.richardson@intel.com>; Jerin Jacob
> Kollanukkaran <jerinj@marvell.com>
> Cc: dev <dev@dpdk.org>; thomas@monjalon.net
> Subject: [EXT] Re: meson build issue
>
> On Thu, 2019-07-04 at 15:01 +0100, Bruce Richardson wrote:
> > On Thu, Jul 04, 2019 at 01:57:14PM +0000, Jerin Jacob Kollanukkaran
> > wrote:
> > >
> > > > -----Original Message-----
> > > > From: Bruce Richardson <
> > > > bruce.richardson@intel.com
> > > > >
> > > > Sent: Thursday, July 4, 2019 7:21 PM
> > > > To: Jerin Jacob Kollanukkaran <
> > > > jerinj@marvell.com
> > > > >
> > > > Cc: dev <
> > > > dev@dpdk.org
> > > > >; Luca Boccassi <
> > > > bluca@debian.org
> > > > >;
> > > > thomas@monjalon.net
> > > >
> > > > Subject: [EXT] Re: meson build issue
> > > >
> > > > On Thu, Jul 04, 2019 at 01:38:01PM +0000, Jerin Jacob
> > > > Kollanukkaran wrote:
> > > > > Anyone else facing this meson build issue in master?
> > > > >
> > > > > Installing
> > > > > /home/jerin/dpdk-next-eventdev/build-x86-default/meson-
> > > >
> > > > private/libdpdk
> > > > > .pc to
> > > > > /home/jerin/dpdk-next-eventdev/build-x86-default/install-
> > > > > root/usr/loca
> > > > > l/lib/pkgconfig Running custom install script '/bin/sh
> > > > > /home/jerin/dpdk-next-eventdev/config/../buildtools/symlink-
> > > > > drivers-
> > > >
> > > > solibs.sh lib dpdk/pmds-19.08'
> > > > > Running custom install script '/usr/bin/sh -c rm -f
> > > >
> > > >
> $MESON_INSTALL_DESTDIR_PREFIX/share/doc/dpdk/guides/.buildinfo'
> > > > > Running custom install script '/usr/bin/sh -c install -D -m0644
> > > >
> > > > $MESON_SOURCE_ROOT/doc/guides/custom.css
> > > >
> $MESON_INSTALL_DESTDIR_PREFIX/share/doc/dpdk/guides/_static/css/c
> > > > us
> > > > tom.css'
> > > > > ## Building cmdline
> > > > > make: Entering directory '/home/jerin/dpdk-next-eventdev/build-
> > > > > x86-
> > > >
> > > > default/install-root/usr/local/share/dpdk/examples/cmdline'
> > > > > pkgconf: unknown option -- define-prefix
> > > >
> > > > What distro are you on? You probably need an updated copy of pkg-
> > > > config or pkgconf.
> > >
> > > It is arch linux(rolling distro)
> > >
> > > $ pkg-config --version
> > > 0.28
> > >
> > > $ pkgconf --version
> > > 0.28
> > >
> >
> > Maybe pkgconf doesn't support that flag yet. If you install pkg-
> > config rather than pkgconf does it make the problem go away? (at least
> > on ubuntu when I tried it the two were mutually exclusive)
> >
> > /Bruce
>
> Support for that flag was added in pkgconf 1.2.0 in January 2017 and pkg-
> config 0.29 in August 2015 - the problem is that version of pkg- config is even
> older, 0.28 from 2013 - strange that Arch doesn't have anything newer?
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.
>
> --
> Kind regards,
> Luca Boccassi
next prev parent reply other threads:[~2019-07-04 14:18 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 ` Jerin Jacob Kollanukkaran [this message]
2019-07-04 14:20 ` [dpdk-dev] [EXT] " Bruce Richardson
2019-07-04 14:44 ` Thomas Monjalon
2019-07-04 15:17 ` Bruce Richardson
2019-07-04 16:08 ` Luca Boccassi
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=BYAPR18MB2424FC02BD21C5FC3751B82CC8FA0@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).