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]

Message-ID: <Pine.LNX.4.64.0710271332440.30465@fbirervta.pbzchgretzou.qr>
Date:	Sat, 27 Oct 2007 13:32:54 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Markus Elfring <Markus.Elfring@....de>
cc:	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: Check handling of kernel build output directory


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
-
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/