From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Markus Elfring <Markus.Elfring@web.de>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: Check handling of kernel build output directory
Date: Sat, 27 Oct 2007 14:21:07 +0200 [thread overview]
Message-ID: <20071027122107.GA30805@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710271332440.30465@fbirervta.pbzchgretzou.qr>
On Sat, Oct 27, 2007 at 01:32:54PM +0200, Jan Engelhardt wrote:
>
> On Oct 26 2007 21:05, Markus Elfring wrote:
> >>> Aren't you supposed to use O= as described by "make help"?
> >>
> >> I expect that both ways should work. I find it easier to use the environment variable
> >> "KBUILD_OUTPUT" because the command line parameter does not need to be repeated on each
> >> make invocation.
> >
> >A wording correction:
> >I expect that both ways should work. I find it easier to use the environment variable
> >"KBUILD_OUTPUT" because it does not need to be repeated on each make invocation like it
> >must happen with the command line parameter "O=".
>
> So why not just...
> export O=/foo/bar
When introducing the make O=...
I was a bit anal about where the definition of O came from so you will see
that in the top-level Makefile we check if O= is defined at the commandline:
ifdef O
ifeq ("$(origin O)", "command line")
KBUILD_OUTPUT := $(O)
endif
endif
"O" is just too vague to be picked up from the environment.
Sam
next prev parent reply other threads:[~2007-10-27 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:31 Check handling of kernel build output directory Markus Elfring
2007-10-26 17:36 ` Vegard Nossum
2007-10-26 18:40 ` Markus Elfring
2007-10-26 19:05 ` Markus Elfring
2007-10-27 11:32 ` Jan Engelhardt
2007-10-27 12:21 ` Sam Ravnborg [this message]
2007-10-26 19:05 ` Sam Ravnborg
2007-10-26 19:25 ` Markus Elfring
2007-10-26 19:47 ` Sam Ravnborg
2007-10-27 5:07 ` Markus Elfring
2007-10-27 7:23 ` Sam Ravnborg
2007-10-27 12:30 ` Markus Elfring
2007-10-27 16:00 ` Markus Elfring
2007-10-27 11:33 ` Jan Engelhardt
2007-10-27 12:41 ` Markus Elfring
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=20071027122107.GA30805@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Markus.Elfring@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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