DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] support older pkg-config
Date: Wed, 20 Nov 2019 22:50:42 +0100	[thread overview]
Message-ID: <1746227.XVKRMh2Mqj@xps> (raw)
In-Reply-To: <9f02ce3e-7e28-79a3-c189-19160e2692b2@intel.com>

18/11/2019 12:48, Ferruh Yigit:
> On 11/15/2019 3:16 PM, Bruce Richardson wrote:
> > Not all pkg-config installs support --define-prefix and --path flags, so
> > ensure we can still build examples without those flags, and that we
> > don't get errors when using test-meson-builds.sh with/without those
> > flags.
> > 
> > Bruce Richardson (2):
> >   devtools: fix example builds with older pkg-config
> >   examples: suppress errors for missing pkg-config path flag
> 
> For Series,
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied, thanks



      reply	other threads:[~2019-11-20 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 10:35 [dpdk-dev] [PATCH] devtools: fix example build with old pkg-config Ferruh Yigit
2019-11-15 10:41 ` Bruce Richardson
2019-11-15 15:16 ` [dpdk-dev] [PATCH v2 0/2] support older pkg-config Bruce Richardson
2019-11-15 15:16   ` [dpdk-dev] [PATCH v2 1/2] devtools: fix example builds with " Bruce Richardson
2019-11-15 15:17   ` [dpdk-dev] [PATCH v2 2/2] examples: suppress errors for missing pkg-config path flag Bruce Richardson
2019-11-18 11:48   ` [dpdk-dev] [PATCH v2 0/2] support older pkg-config Ferruh Yigit
2019-11-20 21:50     ` Thomas Monjalon [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=1746227.XVKRMh2Mqj@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /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).