From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andy Whitcroft <apw@shadowen.org>,
Martin Bligh <mbligh@google.com>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-mm1 compile failure on x86_64
Date: Tue, 26 Sep 2006 09:48:24 +0100 [thread overview]
Message-ID: <1159260504.28313.4.camel@localhost.localdomain> (raw)
In-Reply-To: <4518E4DF.8010007@goop.org>
On Tue, 2006-09-26 at 01:29 -0700, Jeremy Fitzhardinge wrote:
> Andy Whitcroft wrote:
> > 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.
> >> /usr/local/autobench/sources/x86_64-cross/gcc-3.4.0-glibc-2.3.2/bin/x86_64-unknown-linux-gnu-objcopy:
> >> arch/x86_64/boot/compressed/vmlinux.bin: File truncated
> >> make[2]: *** [arch/x86_64/boot/compressed/vmlinux.bin] Error 1
> >> make[1]: *** [arch/x86_64/boot/compressed/vmlinux] Error 2
> >> make: *** [bzImage] Error 2
> >> 09/25/06-09:13:48 Build the kernel. Failed rc = 2
> >> 09/25/06-09:13:49 build: kernel build Failed rc = 1
> >>
> >> Wierd. Same box compiled 2.6.18 fine.
> >>
> >
> > Pretty sure this isn't a space problem, as we have just checked space
> > before the build and I've taken no action since then. Someone did
> > mention "tool chain issue" when it was first spotted. Will check with
> > them and see why they thought that.
> >
>
> Does this box have an older version of binutils (2.15?)? If so, it
> might be getting upset over the patch "note-section" in Andi's queue. I
> know it has been a bit problematic, but I don't know if the problems
> manifest in this way.
I've not seen it manifest like this but it would be worth trying Jan's
patch from
http://lists.xensource.com/archives/html/xen-devel/2006-08/msg01416.html
to see if it helps.
Andi removed an identical patch (from someone else) from his queue due
to http://marc.theaimsgroup.com/?l=linux-kernel&m=115629369729911&w=2 We
have had the patch in the Xen tree for a couple of weeks now with no
reported problems.
Ian.
next prev parent reply other threads:[~2006-09-26 8:48 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
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 [this message]
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=1159260504.28313.4.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=jeremy@goop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.