From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Vivek Gupta <vivek-g@hcl.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding DPDK installation
Date: Tue, 22 Mar 2016 14:36:21 +0100 [thread overview]
Message-ID: <3056682.peQ5fAMurd@xps13> (raw)
In-Reply-To: <488FF59D9020184C9DCF4B4A0DA4781425547192@NDA-HCLT-MBS03.hclt.corp.hcl.in>
2016-03-22 13:13, Vivek Gupta:
> I am trying to install DPDK 2.2 on Ubuntu 14.
Do you just want to compile DPDK or really install it?
Where do you want to install DPDK?
> After configuring all necessary variables in common_linuxapp
> file, I run following two commands
>
> make config T=x86_64-ivshmem-linuxapp-gcc
The "make config" command is useless if using "install T=" after.
> make install T=x86_64-ivshmem-linuxapp-gcc
The install directory is not specified in this command.
> After 'make install T=x86_64-ivshmem-linuxapp-gcc' , installation fails with message as below
>
> **************
> Build complete [x86_64-native-linuxapp-gcc]
> Installation cannot run with T defined and DESTDIR undefined
> ******************************
Why don't you use DESTDIR as suggested?
Or instead of using the old all-in-one "install T=", you can use
the more standard syntax in 3 commands:
make config T=<target>
<adjust settings in .config>
make
make install [DESTDIR=] [prefix=]
> I have gone through following patches:
> http://dpdk.org/dev/patchwork/patch/9270/
> http://dpdk.org/dev/patchwork/patch/9272/
> More interestingly I found that changes suggested in above patches
> were already in place except of below two-
> addition of 'prefix' in file .../doc/build-sdk-quick-txt [ Applied in ]
> addition of 'make install T=X86_64-native-linuxapp-gcc' in file ../doc/guides/prog_guide/dev_kit_root_make_help.rst
These patches have been Superseded by newer (see the State field).
> In file doc/guides/prog_guide/dev_kit_root_make_help.rst , I had "make install DESTDIR=myinstall" which i replaced with "make install DESTDIR=myinstall prefix=/usr"and tried but no success
> so change the content as suggested in patch#9270 as "make install T=x86_64-native-linuxapp-gcc prefix=/usr" but no progress.
>
> Kindly suggest to solve this issue.
Please read the whole doc/guides/prog_guide/dev_kit_root_make_help.rst
and don't hesitate to suggest any change if something is not clear.
Thanks
> ::DISCLAIMER::
[...]
no disclaimer please
next parent reply other threads:[~2016-03-22 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <488FF59D9020184C9DCF4B4A0DA4781425547192@NDA-HCLT-MBS03.hclt.corp.hcl.in>
2016-03-22 13:36 ` Thomas Monjalon [this message]
2016-03-22 13:53 ` Vivek Gupta
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=3056682.peQ5fAMurd@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=vivek-g@hcl.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).