From: David Aldrich <David.Aldrich@EMEA.NEC.COM>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Problem building DPDK libraries
Date: Thu, 17 Nov 2016 15:51:15 +0000 [thread overview]
Message-ID: <e29ff75809884256b9e46732c6ef5d53@EUX13SRV1.EU.NEC.COM> (raw)
Hi
I am trying to build DPDK 16.07.1 on Wind River Linux 8.
'make' fails:
# make
[snip]
CC rte_spinlock.o
AR librte_eal.a
SYMLINK-FILE include/exec-env/rte_interrupts.h
SYMLINK-FILE include/exec-env/rte_kni_common.h
SYMLINK-FILE include/exec-env/rte_dom0_common.h
INSTALL-LIB librte_eal.a
== Build lib/librte_eal/linuxapp/igb_uio
make[6]: *** /lib/modules/4.1.21-rt13-WR8.0.0.10_preempt-rt/build: No such file or directory. Stop.
/root/dpdk-stable-16.07.1/mk/rte.module.mk:79: recipe for target 'igb_uio.ko' failed
Indeed, that 'build' directory does not exist:
# ls /lib/modules/4.1.21-rt13-WR8.0.0.10_preempt-rt/
kernel modules.alias.bin modules.builtin.bin modules.dep.bin modules.order modules.symbols
modules.alias modules.builtin modules.dep modules.devname modules.softdep modules.symbols.bin
Please can someone help me with this?
Best regards
David
next reply other threads:[~2016-11-17 15:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:51 David Aldrich [this message]
2016-11-17 15:59 ` Thomas Monjalon
2016-11-17 16:05 ` David Aldrich
2016-11-17 16:09 ` Wiles, Keith
2016-11-17 16:24 ` David Aldrich
2016-11-17 16:28 ` David Aldrich
2016-11-17 16:47 ` David Aldrich
2016-11-17 16:54 ` Pavey, Nicholas
2016-11-17 16:56 ` David Aldrich
2016-11-17 16:58 ` Pavey, Nicholas
2016-11-17 17:00 ` Wiles, Keith
2016-11-17 17:02 ` David Aldrich
2016-11-17 17:16 ` Wiles, Keith
2016-11-17 17:23 ` David Aldrich
2016-11-17 17:31 ` Thomas Monjalon
2016-11-17 17:27 ` Thomas Monjalon
2016-11-17 18:38 ` Pavey, Nicholas
2016-11-17 16:56 ` Wiles, Keith
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=e29ff75809884256b9e46732c6ef5d53@EUX13SRV1.EU.NEC.COM \
--to=david.aldrich@emea.nec.com \
--cc=users@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).