From: Andi Kleen <ak@suse.de>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: warren@togami.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 thru bk10 amd64 compile failure
Date: 06 Jun 2003 23:39:03 +0200 [thread overview]
Message-ID: <p73smqm6g3s.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <1054917352.28218.3.camel@serpentine.internal.keyresearch.com.suse.lists.linux.kernel>
Bryan O'Sullivan <bos@serpentine.com> writes:
> On Thu, 2003-06-05 at 22:50, Warren Togami wrote:
>
> > kernel-2.5.70, 2.5.70-bk9 and 2.5.70-bk10 all fail compilation here on
> > my amd64 with gcc-3.2.2-10 on stock RedHat GinGin64. Please pardon me
> > if this is a duplicate report, I am now subscribing in order to keep a
> > closer eye on this list.
>
> You're compiling with CONFIG_VT turned off. Turn it on for now, as I
> don't have a patch for that problem yet.
See it as a feature. Compiling with CONFIG_VT off is in 99.999999999%
of all cases a mistake. On AMD64 it is more likely 100% ;-)
Seriously is quite possible that obscure configurations do not compile on amd64
(obscure is anything that is not like arch/x86_64/defconfig ;)
They are not regularly tested. Patches are welcome.
As for CONFIG_VT I think this option should really be wrapped by
CONFIG_EMBEDDED, Turning it off is near always a mistake.
Same for the keyboard drivers in the input layer at least for CONFIG_X86.
This would work with make oldconfig too from 2.4 config files
unlike the current way.
-Andi
next parent reply other threads:[~2003-06-06 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1054878617.3699.134.camel@laptop.suse.lists.linux.kernel>
[not found] ` <1054917352.28218.3.camel@serpentine.internal.keyresearch.com.suse.lists.linux.kernel>
2003-06-06 21:39 ` Andi Kleen [this message]
2003-06-06 21:51 ` 2.5.70 thru bk10 amd64 compile failure Warren Togami
2003-06-06 5:50 Warren Togami
2003-06-06 16:35 ` Bryan O'Sullivan
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=p73smqm6g3s.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warren@togami.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