From: Tejun Heo <htejun@gmail.com>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem making kernel with debian unstable due to make upgrade
Date: Tue, 28 Feb 2006 15:43:37 +0900 [thread overview]
Message-ID: <4403F119.8020509@gmail.com> (raw)
In-Reply-To: <cbec11ac0602271655p70669d4bi99096282a5e0b86e@mail.gmail.com>
Ian McDonald wrote:
> Folks,
>
> If anybody else is banging their heads against the wall and uses
> debian unstable this seems to be due to a make bug in the current
> version.
>
> In particular mine happened with make going from 3.80+3.81.b4-1 to
> 3.80+3.81.rc1-1
>
> There is a bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354602
>
> Just to let you know as I'm sure others of you will soon be as
> frustrated as me - particularly when I have a box that takes an hour
> to compile....
>
I was scratching my head for more than three hours now. Thanks for
notifying. So, make it was. :-(
--
tejun
prev parent reply other threads:[~2006-02-28 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 0:55 Problem making kernel with debian unstable due to make upgrade Ian McDonald
2006-02-28 6:43 ` Tejun Heo [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=4403F119.8020509@gmail.com \
--to=htejun@gmail.com \
--cc=imcdnzl@gmail.com \
--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