From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 379] Build fail using dpdk-setup.sh in RedHat version 3.10.0-862.rt56.804.el7.x86_64
Date: Fri, 03 Jan 2020 05:32:30 +0000 [thread overview]
Message-ID: <bug-379-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=379
Bug ID: 379
Summary: Build fail using dpdk-setup.sh in RedHat version
3.10.0-862.rt56.804.el7.x86_64
Product: DPDK
Version: 17.11
Hardware: x86
OS: All
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: CHANWEN.LIAO@deltaww.com
Target Milestone: ---
Hi,
I was trying to build DPDK environment using dpdk-setup.sh but can't get DPDK
to compile.
$sudo ./dpdk-stable-17.11.5/usertools/dpdk-setup.sh
I type 14(x86_64-native-lunuxapp-gcc) to build DPDK show the errors below:
Configuration done using x86_64-native-linuxapp-gcc
==Build lib
==Build lib/librte_compat
==Build lib/librte_eal
==Build lib/librte_eal/common
==Build lib/librte_eal/linuxapp
==Build lib/librte_eal/linuxapp/eal
==Build lib/librte_eal/linuxapp/igb_uio
make: *** /lib/modules/3.10.0-862.rt56.804.el7.x86_64/build: No such file or
directory. Stop.
make[7]: *** [igb_uio.ko] Error 2
make[6]: *** [igb_uio.] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-01-03 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 5:32 bugzilla [this message]
2020-01-03 10:31 ` [dpdk-dev] [Bug 379] Build fail using dpdk-setup.sh in RedHat version 3.10.0-862.rt56.804.el7.x86_64 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-379-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.