From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 87] build dpdk and example with different gcc version issue
Date: Fri, 31 Aug 2018 03:28:53 +0000 [thread overview]
Message-ID: <bug-87-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=87
Bug ID: 87
Summary: build dpdk and example with different gcc version
issue
Product: DPDK
Version: unspecified
Hardware: x86
OS: FreeBSD
Status: CONFIRMED
Severity: minor
Priority: Low
Component: other
Assignee: dev@dpdk.org
Reporter: xuemingx.zhang@intel.com
Target Milestone: ---
we try different gcc version,results are as follows:
1、Compiled successfully
# gmake install -j1 T=x86_64-native-bsdapp-gcc CC=gcc48
# gmake examples -j1 T=x86_64-native-bsdapp-gcc CC=gcc48
2、Compiled successfully
# gmake install -j1 T=x86_64-native-bsdapp-gcc
# gmake examples -j1 T=x86_64-native-bsdapp-gcc
3、Compiled successfully
# gmake install -j1 T=x86_64-native-bsdapp-gcc
# gmake examples -j1 T=x86_64-native-bsdapp-gcc CC=gcc48
4、Compile failed
# gmake install -j1 T=x86_64-native-bsdapp-gcc CC=gcc48
# gmake examples -j1 T=x86_64-native-bsdapp-gcc
error message:
================== Build examples for x86_64-native-bsdapp-gcc ==
bbdev_app
CC main.o
LD bbdev
/usr/local/bin/ld: cannot find -lrte_common_octeontx
collect2: error: ld returned 1 exit status
gmake[4]: *** [/root/meijuan/dpdk/mk/rte.app.mk:365: bbdev] Error 1
gmake[3]: *** [/root/meijuan/dpdk/mk/rte.extapp.mk:15: all] Error 2
gmake[2]: *** [/root/meijuan/dpdk/mk/rte.extsubdir.mk:22: bbdev_app]
Error 2
gmake[1]: *** [/root/meijuan/dpdk/mk/rte.sdkexamples.mk:26: x86_64-
native-bsdapp-gcc_examples] Error 2
gmake: *** [/root/meijuan/dpdk/mk/rte.sdkroot.mk:96: examples] Error 2
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-08-31 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 3:28 bugzilla [this message]
2018-08-31 10:04 ` [Bug 87] build dpdk and example with different gcc version issue Ferruh Yigit
2018-08-31 17:08 ` Jerin Jacob
2018-09-03 8:51 ` Ferruh Yigit
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-87-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.