From: Ken Offer <koffer@arlut.utexas.edu>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Problem with linuxppc smp.c
Date: Tue, 08 May 2001 15:21:33 -0500 [thread overview]
Message-ID: <3AF8554D.BF250E0A@arlut.utexas.edu> (raw)
Hi all,
Compiling the latest-greatest linuxppc 2.4.5 from
www.fsmlabs.com/linuxppcbk.html yields the following compile-time errors
in arch/ppc/kernel/smp.c:
gcc -D__KERNEL__ -I/usr/src/linuxppc_2_4_5/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-D__powerpc__ -
fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple
-mstring -c -o smp.o smp.c
smp.c: In function `smp_gemini_kick_cpu':
smp.c:670: `i' undeclared (first use in this function)
smp.c:670: (Each undeclared identifier is reported only once
smp.c:670: for each function it appears in.)
smp.c: In function `smp_gemini_setup_cpu':
smp.c:679: `cpu_nr' undeclared (first use in this function)
smp.c: At top level:
smp.c:748: warning: initialization from incompatible pointer type
make[1]: *** [smp.o] Error 1
make[1]: Leaving directory `/usr/src/linuxppc_2_4_5/arch/ppc/kernel'
make: *** [_dir_arch/ppc/kernel] Error 2
I'm compiling the 2.4.5 kernel on a synergy VSS4 board using gcc-2.95.3
and binutils-2.11.90.0.7 installed. The machine-type is configured as
"gemini", since I'm on the VSS4.
Any thoughts? I guess I could try to grok the author's meaning and fix
this... ;-)
--
______________________________________________________________
Kenneth Ray Offer, II
Sr. Systems Analyst
Applied Research Laboratories/SDD
University of Texas at Austin
Office (512) 835-3859 FAX (512) 835-3259
Any opinions expressed above are mine and not necessarily
those of my employer.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-08 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 20:21 Ken Offer [this message]
2001-05-09 10:54 ` Problem with linuxppc smp.c Michael Schmitz
2001-05-11 23:36 ` Val Henson
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=3AF8554D.BF250E0A@arlut.utexas.edu \
--to=koffer@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).