From: Andrew Morton <akpm@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: Martin Bligh <mbligh@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: 2.6.18-mm1 compile failure on x86_64
Date: Tue, 26 Sep 2006 00:07:14 -0700 [thread overview]
Message-ID: <20060926000714.bd12361b.akpm@osdl.org> (raw)
In-Reply-To: <200609260841.27413.ak@suse.de>
On Tue, 26 Sep 2006 08:41:27 +0200
Andi Kleen <ak@suse.de> wrote:
> On Tuesday 26 September 2006 00:39, Martin Bligh wrote:
> > http://test.kernel.org/abat/49037/debug/test.log.0
> >
> > AS arch/x86_64/boot/bootsect.o
> > LD arch/x86_64/boot/bootsect
> > AS arch/x86_64/boot/setup.o
> > LD arch/x86_64/boot/setup
> > AS arch/x86_64/boot/compressed/head.o
> > CC arch/x86_64/boot/compressed/misc.o
> > OBJCOPY arch/x86_64/boot/compressed/vmlinux.bin
> > BFD: Warning: Writing section `.data.percpu' to huge (ie negative) file
> > offset 0x804700c0.
>
> Most likely that is the problem. I don't know what patch it could be
> (none of mine have been merged yet).
That was 2.6.18-mm1 - it has around 300 of "yours" ;)
> Can you bisect?
I was unable to reproduce it. Lack of disk space is suspected.
next prev parent reply other threads:[~2006-09-26 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 22:39 2.6.18-mm1 compile failure on x86_64 Martin Bligh
2006-09-25 22:43 ` Jeff Garzik
2006-09-25 22:50 ` Martin Bligh
2006-09-26 6:41 ` Andi Kleen
2006-09-26 7:07 ` Andrew Morton [this message]
2006-09-26 7:09 ` Andi Kleen
2006-09-26 7:51 ` Andy Whitcroft
2006-09-26 8:29 ` Jeremy Fitzhardinge
2006-09-26 8:48 ` Ian Campbell
2006-09-27 9:17 ` Andy Whitcroft
2006-09-26 12:44 ` Andy Whitcroft
2006-09-27 1:35 ` Eric W. Biederman
2006-09-27 9:58 ` Andre Noll
2006-09-27 10:26 ` Andi Kleen
2006-09-27 11:04 ` Andy Whitcroft
2006-09-27 11:24 ` Ian Campbell
2006-09-27 11:08 ` Ian Campbell
2006-09-27 12:05 ` Andi Kleen
2006-09-27 14:11 ` Eric W. Biederman
2006-09-27 16:53 ` Andy Whitcroft
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=20060926000714.bd12361b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
/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