DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "Ratliff, Stanley" <sratliff@idirect.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Build instructions
Date: Fri, 28 Aug 2015 19:52:32 +0000	[thread overview]
Message-ID: <b8b88f74af5b40db91dface9250877bf@VAUSDITCHM2.idirect.net> (raw)
In-Reply-To: <5da12112633d4a5fa6db7aff19f813d3@VAUSDITCHM2.idirect.net>

Hello again, 

My mistake. Typo. Sorry for the noise. 

Regards,
Stan


> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ratliff, Stanley
> Sent: Friday, August 28, 2015 3:49 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Build instructions
> 
> 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@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@stansubu:~$ cd dpdk
> stanr@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@stansubu:~/dpdk$ ls
> 
> 
> 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.
> _____________________________________________________
> 


_____________________________________________________
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.
_____________________________________________________

  reply	other threads:[~2015-08-28 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 19:49 Ratliff, Stanley
2015-08-28 19:52 ` Ratliff, Stanley [this message]
2015-08-28 19:52 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=b8b88f74af5b40db91dface9250877bf@VAUSDITCHM2.idirect.net \
    --to=sratliff@idirect.net \
    --cc=dev@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).