From: Malcolm Mallardi <magamo@ranka.2y.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre7 MIPS compile errors.
Date: Wed, 24 Apr 2002 14:58:25 -0400 [thread overview]
Message-ID: <20020424145825.A21701@trianna.upcommand.net> (raw)
The MIPS box (an SGI Indy) has been having problems compiling kernels
since I first put Linux on it I've never had a kernel complete the
basic image compile (make vmlinux) between 2.4.16-2.4.18 there were
problems compiling one of the keyboard drivers, 2.4.19-pre5 had the two
problems I'm about to describe, as does 2.4.19-pre7. 2.4.19-pre6
wouldn't even attempt to compile.
It's an R5000/150Mhz, 128M RAM, Newport graphics, Debian Woody, gcc
2.95.4, binutils 2.12.90.0.1 20020307.
First problem seems to be in the ARCs Console support subsystem of the
kernel.
gcc -I /usr/src/linux-2.4.19-pre7/include/asm/gcc -D__KERNEL__
-I/usr/src/linux-2.4.19-pre7/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r5000 -mips2
-Wa,--trap -pipe -nostdinc -I
/usr/lib/gcc-lib/mips-linux/2.95.4/include -DKBUILD_BASENAME=identify
-c -o identify.o identify.c
identify.c: In function `prom_identify_arch':
identify.c:76: warning: `iname' might be used uninitialized in this
function
gcc -I /usr/src/linux-2.4.19-pre7/include/asm/gcc -D__KERNEL__
-I/usr/src/linux-2.4.19-pre7/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r5000 -mips2
-Wa,--trap -pipe -nostdinc -I
/usr/lib/gcc-lib/mips-linux/2.95.4/include -DKBUILD_BASENAME=arc_con
-c -o arc_con.o arc_con.c
arc_con.c:53: warning: initialization from incompatible pointer type
arc_con.c:55: warning: initialization makes integer from pointer
without a cast
arc_con.c:55: initializer element is not computable at load time
arc_con.c:55: (near initialization for `arc_cons.flags')
arc_con.c:60: warning: excess elements in struct initializer
arc_con.c:60: warning: (near initialization for `arc_cons')
make[2]: *** [arc_con.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.19-pre7/arch/mips/arc'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.19-pre7/arch/mips/arc'
make: *** [_dir_arch/mips/arc] Error 2
The second error, I run into when I disable ARC console support, and
attempt to compile again. Not as sure about what causes this one,
though.
gcc -I /usr/src/linux-2.4.19-pre7/include/asm/gcc -D__KERNEL__
-I/usr/src/linux-2.4.19-pre7/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r5000 -mips2
-Wa,--trap -pipe -nostdinc -I
/usr/lib/gcc-lib/mips-linux/2.95.4/include -DKBUILD_BASENAME=signal -c
-o signal.o signal.c
signal.c: In function `do_signal':
signal.c:573: `PER_LINUX' undeclared (first use in this function)
signal.c:573: (Each undeclared identifier is reported only once
signal.c:573: for each function it appears in.)
make[1]: *** [signal.o] Error 1
make[1]: Leaving directory
`/usr/src/linux-2.4.19-pre7/arch/mips/kernel'
make: *** [_dir_arch/mips/kernel] Error 2
Anyway... I'm hoping that this information is useful, if y'all need any
more, please just ask.
--
Malcolm D. Mallardi - Dark Freak At Large
"Captain, we are receiving two-hundred eighty-five THOUSAND hails."
AOL: Nuark UIN: 11084092 Y!: Magamo Jabber: Nuark@jabber.com
http://ranka.2y.net:8008/~magamo/index.htm
next reply other threads:[~2002-04-24 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 18:58 Malcolm Mallardi [this message]
2002-04-25 6:28 ` 2.4.19-pre7 MIPS compile errors Andrey Panin
2002-04-25 13:03 ` [PATCH] arch/mips/kernel/signal.c, still more errors, though Malcolm Mallardi
2002-05-05 7:09 ` 2.4.19-pre7 MIPS compile errors Ralf Baechle
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=20020424145825.A21701@trianna.upcommand.net \
--to=magamo@ranka.2y.net \
--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