From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] devtools: fix example build with old pkg-config
Date: Fri, 15 Nov 2019 10:41:35 +0000 [thread overview]
Message-ID: <20191115104135.GA1517@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20191115103525.94786-1-ferruh.yigit@intel.com>
On Fri, Nov 15, 2019 at 10:35:25AM +0000, Ferruh Yigit wrote:
> The old version of the pkg-config [1] doesn't support '-define-prefix'
> and '--path' arguments which is causing failure building the
> examples [2].
>
Yes for the define-prefix option, no for the path one.
The define-prefix argument is indeed necessary to have a properly working
pkg-config to get cflags/ldflags in this case, so we need to skip the tests
without it. However, the path parameter is only used to properly track the
dependencies of the build to enable rebuilding if the pkg-config file
itself changes. Therefore, having no output from pkg-config --path won't
cause the build to fail, so it's more an optional flag.
/Bruce
next prev parent reply other threads:[~2019-11-15 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 10:35 Ferruh Yigit
2019-11-15 10:41 ` Bruce Richardson [this message]
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
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=20191115104135.GA1517@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--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).