To: spdk@lists.01.org
Subject: [SPDK] Compile ERROR: ‘pci_device_list’ undeclared
Date: Fri, 28 Apr 2017 15:03:35 +0800 [thread overview]
Message-ID: <25be06b4.7c75.15bb35f3e13.Coremail.dlworld0@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi all, there's a compile error when I tried to test the latest SPDK. Is that a code bug or a misconfigure in my environment?
Here is the log:
dpdk# make install T=x86_64-native-linuxapp-gcc DESTDIR=.
dpdk# cd ../spdk
spdk# ./configure --with-dpdk=../dpdk/x86_64-native-linuxapp-gcc
spdk# make
...
LIB libspdk_log_rpc.a
CC lib/env_dpdk/pci.o
In file included from /home/src/dpdk/x86_64-native-linuxapp-gcc/include/rte_pci.h:81:0,
from env_internal.h:55,
from pci.c:34:
pci.c: In function ‘spdk_pci_get_device’:
pci.c:173:22: error: ‘pci_device_list’ undeclared (first use in this function)
TAILQ_FOREACH(dev, &pci_device_list, next) {
^
pci.c:173:22: note: each undeclared identifier is reported only once for each function it appears in
/home/src/spdk/mk/spdk.common.mk:159: recipe for target 'pci.o' failed
make[2]: *** [pci.o] Error 1
/home/src/spdk/mk/spdk.subdirs.mk:35: recipe for target 'env_dpdk' failed
make[1]: *** [env_dpdk] Error 2
/home/src/spdk/mk/spdk.subdirs.mk:35: recipe for target 'lib' failed
make: *** [lib] Error 2
The codes are all latest:
dpdk commit eba33e87ad37626604be7186e746751f99691084
spdk commit 6c172475609120c293b265522c395c52fc5a3bb5
Regards,
Linwen Deng
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3145 bytes --]
next reply other threads:[~2017-04-28 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 7:03 [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-28 15:30 [SPDK] Compile ERROR: ‘pci_device_list’ undeclared Luse, Paul E
2017-04-28 16:11 Harris, James R
2017-04-28 16:14 Luse, Paul E
2017-04-28 16:31 Walker, Benjamin
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=25be06b4.7c75.15bb35f3e13.Coremail.dlworld0@163.com \
--to=spdk@lists.01.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