[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080627160333.GA27072@elte.hu>
Date: Fri, 27 Jun 2008 18:03:33 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Nick Piggin <npiggin@...e.de>, Mark McLoughlin <markmc@...hat.com>,
xen-devel <xen-devel@...ts.xensource.com>,
Eduardo Habkost <ehabkost@...hat.com>,
Vegard Nossum <vegard.nossum@...il.com>,
Stephen Tweedie <sct@...hat.com>, x86@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for
64-bit Xen support
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>> plus -tip auto-testing found another build failure with:
>>
>> http://redhat.com/~mingo/misc/config-Thu_Jun_26_12_46_46_CEST_2008.bad
>>
>> arch/x86/kernel/entry_64.S: Assembler messages:
>> arch/x86/kernel/entry_64.S:1201: Error: invalid character '_' in mnemonic
>> arch/x86/kernel/entry_64.S:1205: Error: invalid character '_' in mnemonic
>> arch/x86/kernel/entry_64.S:1209: Error: invalid character '_' in mnemonic
>> arch/x86/kernel/entry_64.S:1213: Error: invalid character '_' in mnemonic
>
> I'm confused. How did this config both crash and not build?
this problem still reproduces.
i've pushed out all fixes into tip/x86/xen-64bit. That branch combined
with the config above still reproduces the build failure above.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists