All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Makefile asking for mrproper on new checkout with KBUILD_OUTPUT
Date: Thu, 17 Jun 2010 11:45:47 -0400	[thread overview]
Message-ID: <4C1A432B.3020709@panasas.com> (raw)
In-Reply-To: <4C19E01F.2010403@suse.cz>

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

      reply	other threads:[~2010-06-17 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 22:05 Makefile asking for mrproper on new checkout with KBUILD_OUTPUT Boaz Harrosh
2010-06-17  8:43 ` Michal Marek
2010-06-17 15:45   ` Boaz Harrosh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C1A432B.3020709@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.