From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 340] Can't build examples in Ubuntu 18 after commit 4131ad5db from 03/07/2019
Date: Wed, 14 Aug 2019 10:40:06 +0000 [thread overview]
Message-ID: <bug-340-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=340
Bug ID: 340
Summary: Can't build examples in Ubuntu 18 after commit
4131ad5db from 03/07/2019
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: john.soares@accelercomm.com
Target Milestone: ---
Created attachment 65
--> https://bugs.dpdk.org/attachment.cgi?id=65&action=edit
Patch to reverse the commit
After bisecting I found out that the commit
4131ad5db79a016970287282b938ebed2f19bdb3 prevents building the examples.
This is the error message:
"gcc: error: rte_config.h: No such file or directory"
Everything works fine after applying a patch that reverts the mentioned commit.
It might be my mistake but these are the commands that I run from the project's
folder:
make config T=x86_64-native-linux-gcc; cd build; make; make -C ../examples/;
This is the full message from bisecting:
"
4131ad5db79a016970287282b938ebed2f19bdb3 is the first bad commit
commit 4131ad5db79a016970287282b938ebed2f19bdb3
Author: Bruce Richardson <bruce.richardson@intel.com>
Date: Wed Jul 3 17:40:00 2019 +0100
examples: fix pkg-config detection with older make
Make versions before 4.2 did not have support for the .SHELLSTATUS
variable, so use another method to detect shell success.
Fixes: 22119c4591a0 ("examples: use pkg-config in makefiles")
Cc: stable@dpdk.org
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Luca Boccassi <bluca@debian.org>
:040000 040000 a19effc010e643f86f2d3951d86bf8651bec0d63
096fc047eab18a285d7f6d0c783ce47316fcc435 M examples
"
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-08-14 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:40 bugzilla [this message]
2019-10-04 15:09 ` bugzilla
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=bug-340-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).