[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <486927AB.1060006@goop.org>
Date: Mon, 30 Jun 2008 11:36:27 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Ingo Molnar <mingo@...e.hu>
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
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>
>
>>> config and full log can be found at:
>>>
>>> http://redhat.com/~mingo/misc/config-Mon_Jun_30_11_11_51_CEST_2008.bad
>>>
>>>
>> That config doesn't build for me. When I put it in place and do "make
>> oldconfig" it still asks for lots of config options (which I just set
>> to default). But when I build it fails with:
>>
>
> try 'make ARCH=i386 oldconfig' - does it work better that way?
>
Er, we're talking about 64-bit here, aren't we? The log messages are
from a 64-bit kernel.
Well, it was the wrong config anyway, which I guess is the source of
this confusion.
(I thought ARCH= to select 32/64 was going away now that the config has
the bitsize config?)
J
--
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