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: <ffteuq$n3b$1@ger.gmane.org>
Date:	Fri, 26 Oct 2007 21:25:14 +0200
From:	Markus Elfring <Markus.Elfring@....de>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Check handling of kernel build output directory

> So here you do not have a .config file in the directory: /usr/src/obj/linux/2.6.23.1/x86_64/adjusted
> So you are told to create one using some of the available methods.

The README contains the following description.

"...
	"make oldconfig"   Default all questions based on the contents of
			   your existing ./.config file and asking about
			   new config symbols.
	"make silentoldconfig"
			   Like above, but avoids cluttering the screen
			   with questions already answered.
..."

I did not expect that there are more differences besides the "silence".


> The suggested way to fix it is to run "make mrproper"

I did that clean-up step.


> but in your case you would then delete all the output files of your vendor supplied kernel.

I hope not because I've setup symbolic links to point to the current release as far I know
instead of the release "2.6.22.9-0.4-default" that I am using at the moment.


> This is something internal make stuff that is irrelevant in this case.

It is relevant in my case if I want to use different output directories for parallel
builds from the same source directory.

Regards,
Markus

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