From: Sam Ravnborg <sam@ravnborg.org>
To: Petr Vandrovec <petr@vandrovec.name>
Cc: linux-kernel@vger.kernel.org, sam@ravenborg.org, kai@germaschewski.name
Subject: Re: [PATCH] Do not rebuild full kernel tree again and again...
Date: Sun, 12 Mar 2006 18:42:50 +0100 [thread overview]
Message-ID: <20060312174250.GA1470@mars.ravnborg.org> (raw)
In-Reply-To: <20060312172511.GA17936@vana.vc.cvut.cz>
On Sun, Mar 12, 2006 at 06:25:11PM +0100, Petr Vandrovec wrote:
> Hello,
> I've returned back to the computer after month and half, and I've found that
> I cannot reasonably build kernel - just repeating 'make' twice without doing any
> change forced full rebuild of everything, which as far as I can tell is not
> intended behavior. As I did not notice this being reported on the LKML, and
> 2.6.16-rc6 still suffers from this problem, here comes report + patch.
>
> Problem seems to be that new make includes FORCE prerequisite in $? - apparently
> new make treats $? not as 'prerequisities newer than target', but as
> 'prerequisities newer than target or missing'. Due to this $(if) in make rules
> always succeeded as it always received at least 'FORCE', and 'FORCE'
> is not an empty string. So let's filter out 'FORCE' from $? - unless somebody
> can confirm that make 3.81 is broken and unusable for kernel...
This issue has been discussed with Paul D. Smith which also provided
a patch similar to yours.
The patch is in the kbuild queue for 2.6.17.
But we also agreed to postpose this change in make until next stable
release. So if you update your make to latest CVS version you will no
longer see this misbehaviour.
And when 2.6.17 opens up kbuild will be 'fixed' in mainline kernel.
Sam
next prev parent reply other threads:[~2006-03-12 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 17:25 Petr Vandrovec
2006-03-12 17:42 ` Sam Ravnborg [this message]
2006-03-13 6:10 ` Nick Piggin
2006-03-13 9:12 ` Sam Ravnborg
2006-03-13 10:47 ` Nick Piggin
2006-03-13 16:30 ` Sam Ravnborg
2006-03-16 18:31 ` Tejun Heo
2006-03-16 18:37 ` Sam Ravnborg
2006-03-16 19:06 ` Tejun Heo
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=20060312174250.GA1470@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=sam@ravenborg.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome