From: Luca Boccassi <bluca@debian.org>
To: David Marchand <david.marchand@redhat.com>
Cc: bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: pkg-config file generated with meson
Date: Thu, 13 Dec 2018 09:36:32 +0000 [thread overview]
Message-ID: <1544693792.7111.18.camel@debian.org> (raw)
In-Reply-To: <1543841093.5087.56.camel@debian.org>
On Mon, 2018-12-03 at 12:44 +0000, Luca Boccassi wrote:
> On Thu, 2018-11-29 at 15:13 +0100, David Marchand wrote:
> > On Thu, Nov 29, 2018 at 3:08 PM Luca Boccassi <bluca@debian.org>
> > wrote:
> >
> > >
> > > It's true that there is "libdpdk" in the Requires.private
> > > section,
> > > and
> > > probably shouldn't - but at least on Debian stable with pkg-
> > > config
> > > 0.29
> > > it works fine despite that:
> > >
> >
> > Well, this was my first impression when I saw Requires.private but
> > I
> > am not
> > familiar with .pc files.
> >
> >
> > >
> > > $ PKG_CONFIG_PATH=/tmp pkg-config --cflags libdpdk
> > > -include rte_config.h -march=corei7
> > > -I/usr/include/dpdk/../x86_64-linux-gnu/dpdk -I/usr/include/dpdk
> > >
> > > Maybe a newer pkg-config version got smarter? Regardless we
> > > should
> > > look
> > > into it
> > >
> >
> > Mine is older, from rhel7:
> > $ pkg-config --version
> > 0.27.1
>
> I think I found the issue, it looks like a Meson problem, reported
> upstream:
>
> https://github.com/mesonbuild/meson/issues/4583
My fix has been merged, it's available as part of the new 0.49 Meson
release.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-12-13 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 13:55 pkg-config file generated with meson David Marchand
2018-11-29 14:07 ` Luca Boccassi
2018-11-29 14:13 ` David Marchand
2018-12-03 12:44 ` Luca Boccassi
2018-12-03 12:50 ` David Marchand
2018-12-13 9:36 ` Luca Boccassi [this message]
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=1544693792.7111.18.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.