From: Richard Hartensveld <richard@infopact.nl>
To: "linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Compilation errors
Date: Wed, 03 Feb 1999 06:31:52 -0800 [thread overview]
Message-ID: <36B85DD8.CCF82EDE@infopact.nl> (raw)
Hi all,
I'm trying to build the latest cvs tree (first kernel i'm trying to
compile locally on this challenge S)
Does anyone know what's going wrong? the same kernel compiles flawlessly
on my linux/x86 system with a crosscompiler.
Down here is the error.
[root@tux linux]# make zImage
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r8000 -mips2
-pipe -c -o init/main.o init/main.c
/usr/src/linux/include/linux/sched.h: In function `on_sig_stack':
In file included from /usr/src/linux/include/linux/mm.h:4,
from /usr/src/linux/include/linux/slab.h:14,
from /usr/src/linux/include/linux/malloc.h:4,
from /usr/src/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/usr/src/linux/include/linux/sched.h:528: `current' undeclared (first
use this function)
/usr/src/linux/include/linux/sched.h:528: (Each undeclared identifier is
reported only once
/usr/src/linux/include/linux/sched.h:528: for each function it appears
in.)
/usr/src/linux/include/linux/sched.h:530: warning: control reaches end
of non-void function
/usr/src/linux/include/linux/sched.h: In function `sas_ss_flags':
/usr/src/linux/include/linux/sched.h:534: `current' undeclared (first
use this function)
/usr/src/linux/include/linux/sched.h:536: warning: control reaches end
of non-void function
/usr/src/linux/include/linux/sched.h: In function `suser':
/usr/src/linux/include/linux/sched.h:561: `current' undeclared (first
use this function)
/usr/src/linux/include/linux/sched.h: In function `fsuser':
/usr/src/linux/include/linux/sched.h:570: `current' undeclared (first
use this function)
/usr/src/linux/include/linux/sched.h: In function `capable':
/usr/src/linux/include/linux/sched.h:586: `current' undeclared (first
use this function)
/usr/src/linux/include/linux/mm.h: In function `expand_stack':
In file included from /usr/src/linux/include/linux/slab.h:14,
from /usr/src/linux/include/linux/malloc.h:4,
from /usr/src/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/usr/src/linux/include/linux/mm.h:349: `current' undeclared (first use
this function)
init/main.c: In function `do_basic_setup':
init/main.c:1242: `current' undeclared (first use this function)
make: *** [init/main.o] Error 1
Cheers,
Richard
next reply other threads:[~1999-02-03 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-03 14:31 Richard Hartensveld [this message]
1999-02-03 17:12 ` Compilation errors Alex deVries
1999-02-03 20:43 ` Ulf Carlsson
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 2:59 Peter Teoh
2008-07-01 11:21 compilation errors Jean-Francois Moine
2022-04-01 9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01 ` Fabio M. De Francesco
2022-04-01 12:57 ` Stefano Brivio
2022-04-01 13:07 ` Fabio M. De Francesco
2022-04-01 16:09 ` Alison Schofield
2022-04-01 17:58 ` Fabio M. De Francesco
2022-04-01 14:39 ` Fabio M. De Francesco
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=36B85DD8.CCF82EDE@infopact.nl \
--to=richard@infopact.nl \
--cc=linux@cthulhu.engr.sgi.com \
/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.