From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] fix issues with Ubuntu 18.04 compilation
Date: Wed, 03 Jul 2019 17:49:03 +0100 [thread overview]
Message-ID: <d617eea15e704b34c1f31b4ebea7258c0f8bd5d1.camel@debian.org> (raw)
In-Reply-To: <20190703164001.24841-1-bruce.richardson@intel.com>
On Wed, 2019-07-03 at 17:39 +0100, Bruce Richardson wrote:
> This set has two fixes for the build issues on Ubuntu. The first
> patch
> adds in support for older make v4.1, and the second works around a
> problem with pkg-config giving an incorrect prefix in some
> circumstances.
>
> Bruce Richardson (2):
> examples: fix pkg-config detection with older make
> buildtools/test-meson-builds: workaround pkg-config issue
>
> devtools/test-meson-builds.sh | 4 +++-
> examples/bbdev_app/Makefile | 3 +--
> examples/bond/Makefile | 3 +--
> examples/cmdline/Makefile | 3 +--
> examples/distributor/Makefile | 3 +--
> examples/eventdev_pipeline/Makefile | 3 +--
> examples/exception_path/Makefile | 3 +--
> examples/fips_validation/Makefile | 3 +--
> examples/flow_classify/Makefile | 3 +--
> examples/flow_filtering/Makefile | 3 +--
> examples/helloworld/Makefile | 3 +--
> examples/ip_fragmentation/Makefile | 3 +--
> examples/ip_pipeline/Makefile | 3 +--
> examples/ip_reassembly/Makefile | 3 +--
> examples/ipsec-secgw/Makefile | 3 +--
> examples/ipv4_multicast/Makefile | 3 +--
> examples/kni/Makefile | 3 +--
> examples/l2fwd-cat/Makefile | 3 +--
> examples/l2fwd-crypto/Makefile | 3 +--
> examples/l2fwd-jobstats/Makefile | 3 +--
> examples/l2fwd-keepalive/Makefile | 3 +--
> examples/l2fwd/Makefile | 3 +--
> examples/l3fwd-acl/Makefile | 3 +--
> examples/l3fwd-power/Makefile | 3 +--
> examples/l3fwd-vf/Makefile | 3 +--
> examples/l3fwd/Makefile | 3 +--
> examples/link_status_interrupt/Makefile | 3 +--
> examples/load_balancer/Makefile | 3 +--
> examples/packet_ordering/Makefile | 3 +--
> examples/ptpclient/Makefile | 3 +--
> examples/qos_meter/Makefile | 3 +--
> examples/qos_sched/Makefile | 3 +--
> examples/rxtx_callbacks/Makefile | 3 +--
> examples/service_cores/Makefile | 3 +--
> examples/skeleton/Makefile | 3 +--
> examples/tep_termination/Makefile | 3 +--
> examples/timer/Makefile | 3 +--
> examples/vdpa/Makefile | 3 +--
> examples/vhost/Makefile | 3 +--
> examples/vhost_crypto/Makefile | 3 +--
> examples/vhost_scsi/Makefile | 3 +--
> examples/vmdq/Makefile | 3 +--
> examples/vmdq_dcb/Makefile | 3 +--
> 43 files changed, 45 insertions(+), 85 deletions(-)
Series-acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-07-03 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 16:39 Bruce Richardson
2019-07-03 16:40 ` [dpdk-dev] [PATCH 1/2] examples: fix pkg-config detection with older make Bruce Richardson
2019-07-03 16:40 ` [dpdk-dev] [PATCH 2/2] buildtools/test-meson-builds: workaround pkg-config issue Bruce Richardson
2019-07-04 8:39 ` Luca Boccassi
2019-07-04 9:47 ` Bruce Richardson
2019-07-03 16:49 ` Luca Boccassi [this message]
2019-07-03 21:11 ` [dpdk-dev] [PATCH 0/2] fix issues with Ubuntu 18.04 compilation 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=d617eea15e704b34c1f31b4ebea7258c0f8bd5d1.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.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 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).