DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] meson build issue
Date: Thu, 4 Jul 2019 15:01:43 +0100	[thread overview]
Message-ID: <20190704140143.GB439@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <BYAPR18MB24245F60FB53D5588458A530C8FA0@BYAPR18MB2424.namprd18.prod.outlook.com>

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/cus
> > 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

  reply	other threads:[~2019-07-04 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 13:57 Jerin Jacob Kollanukkaran
2019-07-04 14:01 ` Bruce Richardson [this message]
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
2019-07-04 15:04         ` Jerin Jacob Kollanukkaran
  -- strict thread matches above, loose matches on Subject: below --
2019-07-04 13:38 [dpdk-dev] " Jerin Jacob Kollanukkaran
2019-07-04 13:50 ` Bruce Richardson
2019-07-04 13:52   ` David Marchand

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=20190704140143.GB439@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --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).