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 14:50:47 +0100 [thread overview]
Message-ID: <20190704135047.GA439@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <BYAPR18MB2424B8037730F7163A311A7EC8FA0@BYAPR18MB2424.namprd18.prod.outlook.com>
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/local/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/custom.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.
/Bruce
next prev parent reply other threads:[~2019-07-04 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 13:38 Jerin Jacob Kollanukkaran
2019-07-04 13:50 ` Bruce Richardson [this message]
2019-07-04 13:52 ` David Marchand
2019-07-04 13:57 Jerin Jacob Kollanukkaran
2019-07-04 14:01 ` Bruce Richardson
2019-07-04 14:14 ` Luca Boccassi
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=20190704135047.GA439@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).