linux-kernel - Re: Check handling of kernel build output directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 27 Oct 2007 14:21:07 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Markus Elfring <Markus.Elfring@....de>,
	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: Check handling of kernel build output directory

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/