linux-kernel - Re: Makefile asking for mrproper on new checkout with KBUILD

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4C1A432B.3020709@panasas.com>
Date:	Thu, 17 Jun 2010 11:45:47 -0400
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Michal Marek <mmarek@...e.cz>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Makefile asking for mrproper on new checkout with KBUILD_OUTPUT

On 06/17/2010 04:43 AM, Michal Marek wrote:
> On 17.6.2010 00:05, Boaz Harrosh wrote:
>>
>> I get this problem: When a few Header files are changed, like when doing
>> a git checkout the Makefile is complaining about mrproper needed.
>>
>> Now I'm building a:
>> 	make ARCH=arch KBUILD_OUTPUT=.build_arch/
>>
>> But a: 
>> 	make ARCH=arch KBUILD_OUTPUT=.build_arch/ mrproper
>>
>> Will not help. What the Makefile wants is a:
>> 	make mrproper
>>
>> doing the "make mrproper" does solves it.
>> It used to be fine, I'm not sure when it started to break.
>>
>> How can I debug this to see what is the offending files?
> 
> The makefile errors out if the source directory is configured (*),
> because having random object files in the source directory would confuse
> the VPATH build.
> 
> (*) Means: either .config or include/config exists
> 

OK, Thanks. What I see is that when I do:
make ARCH=um KBUILD_OUTPUT=.build_um INSTALL_MOD_PATH=$FS_LOCAL_MOUNT modules_install

I get a phantom empty include/config directory. The INSTALL_MOD_PATH=$FS_LOCAL_MOUNT is
because I'm installing into the uml image file.

This only happens when some include/... header files changed since the last make.
The "make ARCH=um KBUILD_OUTPUT=.build_um" stage is fine only after the modules_install
stage it appears.

> Michal

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