From: Sam Ravnborg <sam@ravnborg.org>
To: Giacomo Catenazzi <cate@debian.org>
Cc: Mike Galbraith <efault@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23.git build error
Date: Sat, 13 Oct 2007 09:16:26 +0200 [thread overview]
Message-ID: <20071013071626.GA28168@uranus.ravnborg.org> (raw)
In-Reply-To: <47105A39.9070406@debian.org>
On Sat, Oct 13, 2007 at 07:40:09AM +0200, Giacomo Catenazzi wrote:
> Mike Galbraith wrote:
> > On Fri, 2007-10-12 at 23:31 +0200, Sam Ravnborg wrote:
> >> On Fri, Oct 12, 2007 at 06:48:58AM +0200, Mike Galbraith wrote:
> >>> Greetings,
> >>>
> >>> Freshly pulled 2.6.23.git failed to build:
> >>>
> >>> make[1]: *** No rule to make target `arch/x86/kernel/asm-offsets.c', needed by `arch/x86/kernel/asm-offsets.s'. Stop.
> >>> make: *** [prepare0] Error 2
> >>> make: *** Waiting for unfinished jobs....
> >> You are the only reporter of this bug.
> >> I do not see it here and I have the asm-offset.c file.
> >
> > Yeah, I noticed nobody else was griping.
>
>
> I also saw this behaiour, but make mrproper solved the problem.
Pulled 2.6.23 tree and did a build
Added latest -linus on top of it.
Did a new build (x86_64).
As expected it failed due to wrong asm symlink but nothing
like the error Mike posted.
So I'm a bit puzzeled here.
I anyone can explain how to reproduce it I will chase it
but otherwise it will be left as a "consequence of
the x86 merge".
Sam
next prev parent reply other threads:[~2007-10-13 7:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 4:48 Mike Galbraith
2007-10-12 21:31 ` Sam Ravnborg
2007-10-13 3:34 ` Mike Galbraith
2007-10-13 5:40 ` Giacomo Catenazzi
2007-10-13 7:16 ` Sam Ravnborg [this message]
2007-10-13 7:35 ` Mike Galbraith
2007-10-13 8:17 ` Sam Ravnborg
2007-10-13 9:44 ` Thomas Gleixner
[not found] ` <1192608832.30373.5.camel@Homer.simpson.net>
2007-10-17 20:06 ` [PATCH] x86: delete vsyscall files during make clean Sam Ravnborg
2007-10-17 20:09 ` Thomas Gleixner
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=20071013071626.GA28168@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=cate@debian.org \
--cc=efault@gmx.de \
--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®