From: Jens Axboe <axboe@kernel.dk>
To: Stefan Hajnoczi <stefanha@redhat.com>, linux-block@vger.kernel.org
Cc: Paymon MARANDI <darwinskernel@gmail.com>
Subject: Re: [PATCH] Revert "make: let src/Makefile set *dir vars properly"
Date: Thu, 14 Apr 2022 06:55:48 -0600 [thread overview]
Message-ID: <4c5803a4-4e69-e107-c2b8-7a3e7733fae2@kernel.dk> (raw)
In-Reply-To: <20220414063651.81341-1-stefanha@redhat.com>
On 4/14/22 12:36 AM, Stefan Hajnoczi wrote:
> This reverts commit 9236f53a8ffe96cc2430f7131bbcba5756b97bc2.
>
> "make install DESTDIR=..." specifies a root directory where files are
> installed. For example, includedir=/usr/include DESTDIR=/a should
> install header files into /a/usr/include.
>
> Commit 9236f53a8ffe removed the includedir=, etc arguments on the make
> command-line in ./Makefile, leaving only prefix=$(DESTDIR)$(prefix). It
> claimed "prefix suffice for setting *dir variables in src/Makefile" but
> this is incorrect. "make install DESTDIR=..." now has no effect and
> files are not installed with a DESTDIR prefix.
>
> The GNU make manual 9.5 Overriding Variables says:
>
> all ordinary assignments of the same variable in the makefile are
> ignored; we say they have been overridden by the command line
> argument.
>
> This explains why it was necessary to set includedir=, etc on the make
> command-line in ./Makefile. We need to override these variables with
> DESTDIR from the command-line so they are not clobbered in src/Makefile
> when config-host.mak is included.
I think this should have gone to io-uring@vger.kernel.org, the patch had
me confused for a second.
--
Jens Axboe
next prev parent reply other threads:[~2022-04-14 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 6:36 [PATCH] Revert "make: let src/Makefile set *dir vars properly" Stefan Hajnoczi
2022-04-14 12:55 ` Jens Axboe [this message]
2022-04-19 7:00 ` Stefan Hajnoczi
2022-04-14 12:55 ` Jens Axboe
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=4c5803a4-4e69-e107-c2b8-7a3e7733fae2@kernel.dk \
--to=axboe@kernel.dk \
--cc=darwinskernel@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=stefanha@redhat.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