From: "Paul D. Smith" <psmith@gnu.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: bug-make@gnu.org, LKML <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net, Art Haas <ahaas@airmail.net>
Subject: Re: kbuild: Problem with latest GNU make rc
Date: Sun, 5 Mar 2006 17:21:08 -0500 [thread overview]
Message-ID: <17419.25684.389269.70457@lemming.engeast.baynetworks.com> (raw)
In-Reply-To: <20060304214026.GB1539@mars.ravnborg.org>
%% Sam Ravnborg <sam@ravnborg.org> writes:
sr> I foresee a lot of mails to lkml the next year or more with this
sr> issue if kept. People do build older kernels and continue to do so
sr> the next long time. Especially the embedded market seem keen to
sr> stay at 2.4 (wonder why), and as such we will see many systems
sr> that keep older kernel src but never make behaviour.
Well, this behavior doesn't exist in 2.4 kernels, since the kernel build
in 2.4 was very different. Nevertheless there are plenty of 2.6 kernels
out there :-).
sr> Suggestion:
sr> We are now warned about an incompatibility in kbuild and we will
sr> fix this asap. But that you postpone this particular behaviour
sr> change until next make release. Maybe you add in this change as
sr> the first thing after the stable relase so all bleeding edge make
sr> users see it and can report issues.
I am willing to postpone this change. However, I can't say how much of
a window this delay will give you: I can say that it's extremely
unlikely that it will be another 3 years before GNU make 3.82 comes out.
sr> It is not acceptable that the kernel links each time we do a make.
sr> We keep track of a version number, we do partly jobs as root etc.
sr> So any updates on an otherwise build tree is a bug - and will be
sr> reported and has to get fixed.
I've modified the kbuild system to collect .PHONY files into a variable,
PHONY, and then used that in the if_changed* macros.
Using this method I've determined that the new version of GNU make works
exactly like the old version under various tests (build from scratch,
rebuild without any changes, rebuild with simple changes, etc.)
I've submitted a patch to linux-kernel implementing this change, with
an appropriate Signed-off-by line.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@gnu.org> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
next prev parent reply other threads:[~2006-03-05 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17413.49617.923704.35763@lemming.engeast.baynetworks.com>
2006-03-04 21:40 ` Sam Ravnborg
2006-03-05 22:21 ` Paul D. Smith [this message]
2006-03-05 23:19 ` Sam Ravnborg
2006-03-06 14:17 ` [kbuild-devel] " Giacomo A. Catenazzi
2006-03-06 15:48 ` Jesper Juhl
2006-03-06 15:58 ` Giacomo A. Catenazzi
2006-03-04 14:43 psmith
2006-03-04 21:20 ` Sam Ravnborg
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=17419.25684.389269.70457@lemming.engeast.baynetworks.com \
--to=psmith@gnu.org \
--cc=ahaas@airmail.net \
--cc=bug-make@gnu.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®