From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Giacomo A. Catenazzi" <cate@debian.org>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"Paul D. Smith" <psmith@gnu.org>,
bug-make@gnu.org, LKML <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net,
"Art Haas" <ahaas@airmail.net>
Subject: Re: [kbuild-devel] Re: kbuild: Problem with latest GNU make rc
Date: Mon, 6 Mar 2006 16:48:10 +0100 [thread overview]
Message-ID: <9a8748490603060748x6fbe715eq4c4a55a040cc6238@mail.gmail.com> (raw)
In-Reply-To: <440C4472.8000509@debian.org>
On 3/6/06, Giacomo A. Catenazzi <cate@debian.org> wrote:
> Sam Ravnborg wrote:
> >> 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.
> >
> > One year would be good. The fixed kernel build will be available in an
> > official kernel in maybe two or three months form now. With current pace
> > we will have maybe 3 more kernel relase until this hits us. And only on
> > bleeding edge machines.
>
> I don't think is a big issue. The short-cut "compile only the necessary
> files" is used mainly by developers.
> Anyway the kernel will remain correct. Maybe for old kernel it take more
> time to build the kernel, but correct.
>
> BTW Debian building tools (IIRC) clean the sources before every kernel
> building process, and in 2.4 (and previous) it was high recommended to
> clean and recompile all kernel before any changes, so no big issue in
> these cases.
> I don't know other "normal use", but I think it is not a big issue if
> people will need a complete build in the rare (IMHO) case that they
> want to recompile kernel (with small patches or changes in configuration).
>
Rebuilding the kernel tens (or hundreds) of times may be rare for most
ordinary users, but it's quite common for kernel developers.
Rebuilding the entire kernel every time you make a small change is a
big problem and cost a lot of people a lot of time - and the people
who will bear the cost are the ones who have to build many kernels.
IMHO this is a big problem.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-03-06 15:48 UTC|newest]
Thread overview: 6+ 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
2006-03-05 23:19 ` Sam Ravnborg
2006-03-06 14:17 ` [kbuild-devel] " Giacomo A. Catenazzi
2006-03-06 15:48 ` Jesper Juhl [this message]
2006-03-06 15:58 ` Giacomo A. Catenazzi
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=9a8748490603060748x6fbe715eq4c4a55a040cc6238@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=ahaas@airmail.net \
--cc=bug-make@gnu.org \
--cc=cate@debian.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=psmith@gnu.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®