From: sharanya k <ksharanya.97@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Getting error while configuring dpdk-reg.
Date: Mon, 5 Feb 2018 11:46:11 +0530 [thread overview]
Message-ID: <CAHJ=+w4b7TQrWdj_GtvDMkwXbx+qCh5yi1k5GWaftr+ORRNK7A@mail.gmail.com> (raw)
Hi,
I have installed dpdk-stable-17.08.1.While configuring dpdk, I tried
to set the dpdk environment to build x86_64-native-linuxapp-gcc. But
it shows some errors as follows,
In file included from
/home/ladmin/dpdk-stable-17.08.1/lib/librte_eal/linuxapp/eal/eal.c:57:0:
/home/ladmin/dpdk-stable-17.08.1/x86_64-native-linuxapp-gcc/include/rte_debug.h:82:5:
warning: "RTE_LOG_LEVEL" is not defined [-Wundef]
#if RTE_LOG_LEVEL >= RTE_LOG_DEBUG
^
In file included from
/home/ladmin/dpdk-stable-17.08.1/lib/librte_eal/linuxapp/eal/eal.c:58:0:
/home/ladmin/dpdk-stable-17.08.1/x86_64-native-linuxapp-gcc/include/rte_memory.h:81:5:
warning: "RTE_CACHE_LINE_SIZE" is not defined [-Wundef]
#if RTE_CACHE_LINE_SIZE == 64
^
/home/ladmin/dpdk-stable-17.08.1/x86_64-native-linuxapp-gcc/include/rte_memory.h:83:7:
warning: "RTE_CACHE_LINE_SIZE" is not defined [-Wundef]
#elif RTE_CACHE_LINE_SIZE == 128
^
/home/ladmin/dpdk-stable-17.08.1/x86_64-native-linuxapp-gcc/include/rte_memory.h:86:2:
error: #error "Unsupported cache line size"
#error "Unsupported cache line size"
^
In file included from
/home/ladmin/dpdk-stable-17.08.1/lib/librte_eal/linuxapp/eal/eal.c:61:0:
/home/ladmin/dpdk-stable-17.08.1/x86_64-native-linuxapp-gcc/include/rte_eal.h:85:35:
error: \u2018RTE_MAX_LCORE\u2019 undeclared here (not in a function)
enum rte_lcore_role_t lcore_role[RTE_MAX_LCORE]; /**< State of cores. */
Can you please help me to rectify this error.
Regards,
sharanya
next reply other threads:[~2018-02-05 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 6:16 sharanya k [this message]
2018-02-05 13:57 ` Wiles, Keith
2018-02-06 7:36 ` sharanya k
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='CAHJ=+w4b7TQrWdj_GtvDMkwXbx+qCh5yi1k5GWaftr+ORRNK7A@mail.gmail.com' \
--to=ksharanya.97@gmail.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).