From: Keith M Wesolowski <wesolows@foobazco.org>
To: sparclinux@vger.kernel.org
Subject: Re: kernel 2.4.25-pre8 fails to build for sparc32
Date: Fri, 06 Feb 2004 02:59:51 +0000 [thread overview]
Message-ID: <20040206025951.GA27446@foobazco.org> (raw)
In-Reply-To: <20040206012437.GB2057@tintin>
On Fri, Feb 06, 2004 at 02:24:38AM +0100, Nicolas Boullis wrote:
> First of all, sorry if I'm doing something wrong with this report, I'm
> still quite a newbie on this list...
>
> I just tried to build a sparc32 kernel for my Ultra5. (I know this is
> sparc64 hardware, but I need to test some things with a sparc32 kernel,
> and I think it's supposed to work fine...) Unfortunately, the build
> fails with the following message:
I think you're confused. You probably mean you want to use a 32-bit
userland, which you can do just fine with a sparc64 kernel. The
sparc32 kernel does not support ultrasparc CPUs nor any of the
associated hardware in ultras. Please do not bother trying to make it
work. Use ARCH=sparc64 and all will be well.
--
Keith M Wesolowski
next prev parent reply other threads:[~2004-02-06 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 1:24 kernel 2.4.25-pre8 fails to build for sparc32 Nicolas Boullis
2004-02-06 2:59 ` Keith M Wesolowski [this message]
2004-02-06 22:16 ` Nicolas Boullis
2004-02-06 22:36 ` Keith M Wesolowski
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=20040206025951.GA27446@foobazco.org \
--to=wesolows@foobazco.org \
--cc=sparclinux@vger.kernel.org \
/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.