DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Aldrich <David.Aldrich@emea.nec.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
	"Pavey, Nicholas" <npavey@akamai.com>,
	users@dpdk.org
Subject: Re: [dpdk-users] Problem building DPDK libraries
Date: Thu, 17 Nov 2016 18:31:50 +0100	[thread overview]
Message-ID: <2397934.hKp71BKfuN@xps13> (raw)
In-Reply-To: <99316d4c290d4f2dbf55f0cebe0ddf47@EUX13SRV1.EU.NEC.COM>

2016-11-17 17:23, David Aldrich:
> # make install T=x86_64-native-linuxapp-gcc install
> Installation cannot run with T defined and DESTDIR undefined

Extract of "make help":
        install T=       configure, build and install a target in DESTDIR
        install          install optionally staged in DESTDIR

So "install T=" is equivalent to
	make config
	make
	make install
But install cannot be done without DESTDIR.

  reply	other threads:[~2016-11-17 17:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 15:51 David Aldrich
2016-11-17 15:59 ` Thomas Monjalon
2016-11-17 16:05   ` David Aldrich
2016-11-17 16:09     ` Wiles, Keith
2016-11-17 16:24       ` David Aldrich
2016-11-17 16:28         ` David Aldrich
2016-11-17 16:47         ` David Aldrich
2016-11-17 16:54           ` Pavey, Nicholas
2016-11-17 16:56             ` David Aldrich
2016-11-17 16:58               ` Pavey, Nicholas
2016-11-17 17:00               ` Wiles, Keith
2016-11-17 17:02                 ` David Aldrich
2016-11-17 17:16                   ` Wiles, Keith
2016-11-17 17:23                     ` David Aldrich
2016-11-17 17:31                       ` Thomas Monjalon [this message]
2016-11-17 17:27                   ` Thomas Monjalon
2016-11-17 18:38                   ` Pavey, Nicholas
2016-11-17 16:56           ` 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=2397934.hKp71BKfuN@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=David.Aldrich@emea.nec.com \
    --cc=keith.wiles@intel.com \
    --cc=npavey@akamai.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).