From: psmith@gnu.org
To: linux-kernel@vger.kernel.org
Subject: kbuild: Problem with latest GNU make rc
Date: Sat, 4 Mar 2006 09:43:59 -0500 [thread overview]
Message-ID: <17417.42927.851653.114068@lemming.engeast.baynetworks.com> (raw)
Hi all;
An incompatibility between kbuild and the latest GNU make 3.81 release
candidate has been uncovered by Art Haas. He reports that when building
current kernels with the latest GNU make rc, everything will always be
rebuilt every time.
I've done an analysis of the issue and reported my findings on
Wednesday, 1 March to the kbuild-devel mailing list (which, according to
its archives, hasn't had any messages go through since 31 Jan--is anyone
approving them anymore?) and to the bug-make mailing list (but a
corruption in lists.gnu.org's TMDA database last week has caused a huge
backlog which is only now being cleared).
For full details you can find an archived copy of my message here:
http://lists.gnu.org/archive/html/bug-make/2006-03/msg00003.html
The problem is that the new behavior is (I believe) correct. If I'm
right then this leaves us with a bit of a tricky situation to manage.
If anyone has an opinion or would like to discuss the situation, please
follow up to my email on bug-make@gnu.org (I would prefer to hold the
discussion there since I don't subscribe to linux-kernel).
I would like to come to some kind of decision on this quickly so I can
make an official 3.81 release soon.
Cheers!
--
-------------------------------------------------------------------------------
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 reply other threads:[~2006-03-04 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 14:43 psmith [this message]
2006-03-04 21:20 ` Sam Ravnborg
[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
2006-03-05 23:19 ` 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=17417.42927.851653.114068@lemming.engeast.baynetworks.com \
--to=psmith@gnu.org \
--cc=linux-kernel@vger.kernel.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®