On 8/28/15, 2:49 PM, "dev on behalf of Ratliff, Stanley"
<dev-bounces at dpdk.org on behalf of sratliff at idirect.net> wrote:

>Hello everyone, 
>
>I'm a DPDK newbie, so my apologies for the na?ve question. I'm trying to
>use the instructions at http://dpdk.org/doc/quick-start.
>
>I've cloned the DPDK repo, & started with the make command. I got:
>
>stanr at stansubu:~$ git clone http://dpdk.org/git/dpdk
>Cloning into 'dpdk'...
>remote: Counting objects: 30823, done.
>remote: Compressing objects: 100% (6281/6281), done.
>remote: Total 30823 (delta 24336), reused 30823 (delta 24336)
>Receiving objects: 100% (30823/30823), 21.82 MiB | 1.04 MiB/s, done.
>Resolving deltas: 100% (24336/24336), done.
>Checking connectivity... done.
>stanr at stansubu:~$ cd dpdk
>stanr at stansubu:~/dpdk$ make config T=x86_64-default-linuxapp-gcc
>make[1]: *** No rule to make target
>`/home/stanr/dpdk/config/defconfig_x86_64-default-linuxapp-gcc', needed
>by `/home/stanr/dpdk/build/.config'.  Stop.
>make: *** [config] Error 2
>stanr at stansubu:~/dpdk$ ls

Looks like the docs need to be updated we are changed
x86_64-native-linuxapp-gcc look in the config directory for the base names
and remove the defconfig_ to see what the new names are to be used.
>
>
>Are the instructions out of date?
>
>Regards,
>Stan
>
>
>_____________________________________________________
>This electronic message and any files transmitted with it contains
>information from iDirect, which may be privileged, proprietary
>and/or confidential. It is intended solely for the use of the individual
>or entity to whom they are addressed. If you are not the original
>recipient or the person responsible for delivering the email to the
>intended recipient, be advised that you have received this email
>in error, and that any use, dissemination, forwarding, printing, or
>copying of this email is strictly prohibited. If you received this email
>in error, please delete it and immediately notify the sender.
>_____________________________________________________
>
>


? 
Regards,
++Keith
Intel Corporation



Reply via email to