From: Pete Zaitcev <zaitcev@redhat.com>
To: Marc@SoftwareHackery.Com, <linux-kernel@vger.kernel.org>
Subject: Re: Build problems 2.4.4 on SPARC
Date: Wed, 2 May 2001 20:14:38 -0400 [thread overview]
Message-ID: <200105030014.f430EcO25964@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.988827960.5573.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.988827960.5573.linux-kernel2news@redhat.com>
> While trying to compile the 2.4.4 kernel on a SPARC-20, I encounter the
> following error.
> make[1]: Entering directory `/usr/src/linux-2.4.4/mm'
> make all_targets
> make[2]: Entering directory `/usr/src/linux-2.4.4/mm'
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes
> -O2 -fomit-frame-pointer -fno-strict-aliasing -m32 -pipe -mno-fpu
> -fcall-used-g5 -fcall-used-g7 -c -o memory.o memory.c
> memory.c:183: macro `pmd_alloc' used with too many (3) args
Known problem... For some reason, even current vger CVS has it.
You might want to try Eirik's patch, but I have not idea if
it is correct.
http://marc.theaimsgroup.com/?l=linux-sparc&m=98731698113169&w=2
IMHO, sparc needs a port maintainer. Obviously, DaveM has barely
enough time to deal with sparc64. Unfortunately it is not a position
for weak (like myself). At various times I, Uzi, and Anton tried
that crown for size, but it is way too big and heavy.
-- Pete
next parent reply other threads:[~2001-05-03 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.988827960.5573.linux-kernel2news@redhat.com>
2001-05-03 0:14 ` Pete Zaitcev [this message]
2001-05-02 22:22 Build problems 2.4.4 on SPARC Marc Evans
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=200105030014.f430EcO25964@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=Marc@SoftwareHackery.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