DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: khemendra kumar <khemendra.kumar13@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Sirshak Das <sirshak.das@arm.com>,
	"Brian Brooks" <Brian.Brooks@arm.com>
Subject: Re: [dpdk-dev] [Dpdk-pktgen]dpdk pktgen build failed on x86
Date: Wed, 11 Jul 2018 14:17:26 +0000	[thread overview]
Message-ID: <82B9D0A3-B5C3-4A36-8EDB-20BCA37DF910@intel.com> (raw)
In-Reply-To: <17AE2F7F-BFE6-4E00-B9E1-19F6685AFB95@intel.com>



> On Jul 11, 2018, at 8:21 AM, Wiles, Keith <keith.wiles@intel.com> wrote:
> 
> 
> 
>> On Jul 11, 2018, at 6:47 AM, khemendra kumar <khemendra.kumar13@gmail.com> wrote:
>> 
>> Hi All,
>> 
>> Kindly help to check below compile error in DPDK Pkt-gen on x86.
>> 
>> I am following instructions from "
>> http://pktgen-dpdk.readthedocs.io/en/latest/getting_started.html"
>> 
>> *Below cmd I followed:*
>> sudo make config T=x86_64-native-linuxapp-gcc
>> sudo make
>> 
>> sudo make install
>> sudo make RTE_SDK=/home/root1/khem/dpdk
>> 
>> *Below is error log:*
>> INSTALL-APP dpdk-test-eventdev
>> INSTALL-MAP dpdk-test-eventdev.map
>> Build complete [x86_64-native-linuxapp-gcc]
>> root1@compute-201:~/khem/dpdk$ sudo make install
>> make[1]: Nothing to be done for 'pre_install'.
>> ================== Installing /usr/local/
>> Installation in /usr/local/ complete
>> root1@compute-201:~/khem/dpdk$ cd ../pktgen-dpdk/
>> root1@compute-201:~/khem/pktgen-dpdk$ sudo make
>> RTE_SDK=/home/root1/khem/dpdk
>> == lib
>> == common
>> == lua
>> == src
>> == cli
>> == app
>> CC cli-functions.o
>> In file included from /home/root1/khem/pktgen-dpdk/app/pktgen.h:87:0,
>>                from /home/root1/khem/pktgen-dpdk/app/cli-functions.c:28:
>> /home/root1/khem/pktgen-dpdk/app/pktgen-port-cfg.h: In function
>> ‘rte_eth_txconf_dump’:
>> /home/root1/khem/pktgen-dpdk/app/pktgen-port-cfg.h:289:5: error: ‘struct
>> rte_eth_txconf’ has no member named ‘txq_flags’
>>  tx->txq_flags);
> 
> Looks like you are using the HEAD of DPDK and that has changed for 18.08. use 18.05 version of DPDK for pktgen if you can. Pktgen and your application do not need to use the same version of DPDK unless you need some specific features in DPDK for Pktgen.
> 

I pushed a new version of Pktgen 3.5.2 that works back to at least DPDK version 18.02.

>>    ^
>> /home/root1/khem/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target
>> 'cli-functions.o' failed
>> make[2]: *** [cli-functions.o] Error 1
>> /home/root1/khem/dpdk/mk/rte.extapp.mk:19: recipe for target 'pktgen' failed
>> make[1]: *** [pktgen] Error 2
>> /home/root1/khem/dpdk/mk/rte.extsubdir.mk:21: recipe for target 'app' failed
>> make: *** [app] Error 2
>> root1@compute-201:~/khem/pktgen-dpdk$
>> 
>> Thanks & Regards
>> khem
> 
> Regards,
> Keith

Regards,
Keith


  reply	other threads:[~2018-07-11 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 11:47 khemendra kumar
2018-07-11 13:04 ` Wiles, Keith
2018-07-11 13:21 ` Wiles, Keith
2018-07-11 14:17   ` Wiles, Keith [this message]
2018-07-11 14:26     ` khemendra kumar
2018-07-11 14:59       ` 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=82B9D0A3-B5C3-4A36-8EDB-20BCA37DF910@intel.com \
    --to=keith.wiles@intel.com \
    --cc=Brian.Brooks@arm.com \
    --cc=dev@dpdk.org \
    --cc=khemendra.kumar13@gmail.com \
    --cc=sirshak.das@arm.com \
    /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).