DPDK usage discussions
 help / color / mirror / Atom feed
From: sharanya k <ksharanya.97@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Getting error while configuring dpdk-reg.
Date: Tue, 6 Feb 2018 13:06:43 +0530	[thread overview]
Message-ID: <CAHJ=+w4H7x8vZvRZpGcaOGQHUqn0v6MPtDZBv1kR80cmbtRZvA@mail.gmail.com> (raw)
In-Reply-To: <93CCD638-8EE6-417A-B58B-5C66453FA95E@intel.com>

I got it sir.Thank you

On Mon, Feb 5, 2018 at 7:27 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
>
>> On Feb 5, 2018, at 12:16 AM, sharanya k <ksharanya.97@gmail.com> wrote:
>>
>> 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 give me the directory and command line used, plus the OS type and version?
>
> I normally do the following
>
> # cd <dpdk-top-directory>
> # export RTE_SDK=`pwd`
> # export RTE_TARGET=x86_64-native-linuxapp-gcc
> # make install T=x86_64-native-linuxapp-gcc
>
> You will get a warning at the end of the build, but only because I used ‘install’ and did not give the install directory.
> The command does not install the code, but builds the x86_64-native-linuxapp-gcc directory.
>
> As a side note I use two bash alias scripts to setup and build DPDK, just so I do not have to type it all out.
> Here they are if you want to used them
>
> function _rte() {
>     if [ "$1" != "" ]; then
>         export RTE_SDK=`pwd`
>         export RTE_TARGET=`basename $1`
>         echo "RTE_SDK: "$RTE_SDK " RTE_TARGET: "$RTE_TARGET
>     else
>         echo "Currently RTE_SDK: "$RTE_SDK " RTE_TARGET: "$RTE_TARGET
>     fi
> }
>
> function _bld() {
>     echo make -C ${RTE_SDK} install T=${RTE_TARGET} $@ -j
>     make -C ${RTE_SDK} install T=${RTE_TARGET} $@ -j
> }
>
> alias rte=_rte $@
> alias bld=_bld $@
>
>
> Then cd into top level dpdk directory
>
> # rte x86_64-native-linuxapp-gcc
> # rte          # just gives the current variable state
>
> or
> # rte x86<tab>   # if the x86_64-native-linuxapp-gcc directory exists
>
> # bld      # will cd to RTE_SDK and do the build and return to current directory
>
>>
>> Can you please help me to rectify this error.
>>
>> Regards,
>> sharanya
>
> Regards,
> Keith
>

      reply	other threads:[~2018-02-06  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  6:16 sharanya k
2018-02-05 13:57 ` Wiles, Keith
2018-02-06  7:36   ` sharanya k [this message]

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=+w4H7x8vZvRZpGcaOGQHUqn0v6MPtDZBv1kR80cmbtRZvA@mail.gmail.com' \
    --to=ksharanya.97@gmail.com \
    --cc=keith.wiles@intel.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).