From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
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:52:09 +0200 [thread overview]
Message-ID: <CAJFAV8ysjPdxDzBB=PCemrfxXq+VYpus4yA6Ddx0NO5j_Ay5MA@mail.gmail.com> (raw)
In-Reply-To: <20190704135047.GA439@bricha3-MOBL.ger.corp.intel.com>
On Thu, Jul 4, 2019 at 3:51 PM Bruce Richardson <bruce.richardson@intel.com>
wrote:
> 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.
>
>
I got the same error on my rhel 7.6.
--
David Marchand
next prev parent reply other threads:[~2019-07-04 13:52 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
2019-07-04 13:52 ` David Marchand [this message]
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='CAJFAV8ysjPdxDzBB=PCemrfxXq+VYpus4yA6Ddx0NO5j_Ay5MA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=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).