On Thu, 30 Nov 2000, Rick wrote:
>
> what sort of errors are you seeing...I was able to compile 2.4t10 fine on
> my potato->woody system, athlon box. Just had issues with getting my
> soundblaster to work happy.
>
Well, I just tried it again, and this is what's showing on my screen (only
copied a small part, my screen size is still in the out-of-the-box
setting):
/usr/src/linux/include/linux/interrupt.h:160: `current' undeclared (first
use in this function)
/usr/src/linux/include/linux/interrupt.h: In function
`tasklet_hi_schedule':
/usr/src/linux/include/linux/interrupt.h:174: `current' undeclared (first
use in this function)
In file included from /usr/src/linux/include/linux/string.h:21,
from /usr/src/linux/include/linux/fs.h:23,
from /usr/src/linux/include/linux/capability.h:17,
from /usr/src/linux/include/linux/binfmts.h:5,
from /usr/src/linux/include/linux/sched.h:9,
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/asm/string.h: In function `__constant_memcpy3d':
/usr/src/linux/include/asm/string.h:305: `current' undeclared (first use
in this function)
/usr/src/linux/include/asm/string.h: In function `__memcpy3d':
/usr/src/linux/include/asm/string.h:312: `current' undeclared (first use
in this function)
make[1]: *** [init/main.o] Error 1
make[1]: Leaving directory `/usr/src/linux'
make: *** [stamp-build] Error 2
I thought this kind of message was common for the new gcc, but then again,
that's just my thought.
I sure would like it to work, 'cause I like compiling my own kernel.
Thanks for the help!
--
Ray's Rule of Precision:
Measure with a micrometer. Mark with chalk. Cut with an axe.
