From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 288] Target name recorded wrong when try to build dpdk with x86_64-native-linux-gcc
Date: Thu, 30 May 2019 15:47:21 +0000 [thread overview]
Message-ID: <bug-288-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=288
Bug ID: 288
Summary: Target name recorded wrong when try to build dpdk with
x86_64-native-linux-gcc
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: minor
Priority: Normal
Component: mk
Assignee: dev@dpdk.org
Reporter: jasvinder.singh@intel.com
Target Milestone: ---
When build dpdk using x86_64-native-linux-gcc target. At the end, it publish
wrong target name x86_64-native-linuxapp-gcc instead of
x86_64-native-linux-gcc.
Log info:
$make install T=x86_64-native-linux-gcc -j
Configuration done using x86_64-native-linux-gcc
== Build lib
== Build lib/librte_kvargs
== Build lib/librte_cfgfile
SYMLINK-FILE include/rte_cfgfile.h
CC rte_cfgfile.o
SYMLINK-FILE include/rte_kvargs.h
CC rte_kvargs.o
<snip>
INSTALL-APP testpipeline
INSTALL-MAP testpipeline.map
INSTALL-APP testbbdev
INSTALL-MAP testbbdev.map
INSTALL-APP testpmd
INSTALL-MAP testpmd.map
LD test
INSTALL-APP test
INSTALL-MAP test.map
Build complete [x86_64-native-linuxapp-gcc] <------
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-05-30 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-288-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).