From: Pete Zaitcev <zaitcev@redhat.com>
To: fabrizio.gennari@philips.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.6 does not compile on Sparc
Date: Tue, 10 Jul 2001 14:38:18 -0400 [thread overview]
Message-ID: <200107101838.f6AIcI606442@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.994784040.20448.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.994784040.20448.linux-kernel2news@redhat.com>
> We have a problem with kernel 2.4.6 on a Sparc. [...]
Next time, please be so kind to fold your lines properly.
Now, if you a true hacker, you might want to give a whirl to this:
http://people.redhat.com/zaitcev/linux/linux-2.4.6-mallorn.diff
It certainly compiles, but does not work too well.
It may be a good start if you want to fix sparc(32).
Otherwise, forget it and use something else.
-- Pete
next parent reply other threads:[~2001-07-10 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.994784040.20448.linux-kernel2news@redhat.com>
2001-07-10 18:38 ` Pete Zaitcev [this message]
2001-07-11 5:55 ` Kernel 2.4.6 does not compile on Sparc Alex Buell
2001-07-10 16:51 fabrizio.gennari
2001-07-10 17:27 ` Doug McNaught
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=200107101838.f6AIcI606442@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=fabrizio.gennari@philips.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox