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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4C19E01F.2010403@suse.cz>
Date:	Thu, 17 Jun 2010 10:43:11 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Boaz Harrosh <bharrosh@...asas.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Makefile asking for mrproper on new checkout with KBUILD_OUTPUT

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

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