Message-ID: <451A41B7.7040806@shadowen.org>
Date: Wed, 27 Sep 2006 10:17:43 +0100
From: Andy Whitcroft <apw@shadowen.org>
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@XenSource.com>
CC: Jeremy Fitzhardinge <jeremy@goop.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
References: <45185A93.7020105@google.com> <4518DC0B.10207@shadowen.org>	 <4518E4DF.8010007@goop.org> <1159260504.28313.4.camel@localhost.localdomain>
In-Reply-To: <1159260504.28313.4.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2597
Lines: 59

Ian Campbell wrote:
> 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.

Ok.  To confirm, this seems to be a tool chain age issue.  This seems to
be triggered by the, x86_64-mm-note-section patch.  Reverting that patch
and installing the replacement as at the above URL seems to get us a
built kernel.

Not that it works yet ... but one step forward.

-apw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/