View previous topic :: View next topic |
Author |
Message |
LeChuck n00b
Joined: 11 Aug 2002 Posts: 31
|
Posted: Fri Feb 28, 2003 6:01 pm Post subject: Kernel Recompile Woes |
|
|
I'm trying to recompile my kernel, however I'm running into this problem. It seems to stop with the same error everytime. For the life of me cannot figure out whats wrong Heres the output at the crash point
Code: | gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-ck4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=ptrace -c -o ptrace.o ptrace.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-ck4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=timer -c -o timer.o timer.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-ck4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=user -c -o user.o user.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-ck4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=signal -c -o signal.o signal.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-ck4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -nostdinc -iwithprefix include -DKBUILD_BASENAME=sys -c -o sys.o sys.c
In file included from sys.c:7:
/usr/src/linux-2.4.20-ck4/include/linux/module.h: In function `print_symbol':
/usr/src/linux-2.4.20-ck4/include/linux/module.h:434: `ESRCH' undeclared (first use in this function)
/usr/src/linux-2.4.20-ck4/include/linux/module.h:434: (Each undeclared identifier is reported only once
/usr/src/linux-2.4.20-ck4/include/linux/module.h:434: for each function it appears in.)
sys.c: At top level:
sys.c:494: warning: static declaration for `set_user' follows non-static
make[2]: *** [sys.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.20-ck4/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20-ck4/kernel'
make: *** [_dir_kernel] Error 2 |
|
|
Back to top |
|
|
BonezTheGoon Bodhisattva
Joined: 14 Jun 2002 Posts: 1408 Location: Albuquerque, NM -- birthplace of Microsoft and Gentoo
|
Posted: Fri Feb 28, 2003 7:26 pm Post subject: |
|
|
Are you running the command . . .
Code: | make dep && make clean bzImage modules modules_install |
? It will remove any stale files using the "make clean" option. Beyond that simple guess give us some more information about what you are doing, is the error the exact same lines each time in the sys.c?
Regards,
BonezTheGoon |
|
Back to top |
|
|
LeChuck n00b
Joined: 11 Aug 2002 Posts: 31
|
Posted: Sat Mar 01, 2003 12:05 am Post subject: |
|
|
Thanks for the reply Bonez, I haven't installed any as modules so I just use
Code: | make dep && make clean bzImage |
I've tried doing both make mrproper and make clean but doesn't make a difference The errors are exacly the same everytime. What extra info do you need? |
|
Back to top |
|
|
xuttuh n00b
Joined: 05 Jan 2003 Posts: 26
|
Posted: Sat Mar 01, 2003 8:04 am Post subject: |
|
|
after you do a make mrproper you have to do a make menuconfig (or one of the others) to remake some of the config files, I learned that the hard way
Tim _________________ "Bad spellers of the world untie" |
|
Back to top |
|
|
LeChuck n00b
Joined: 11 Aug 2002 Posts: 31
|
Posted: Sat Mar 01, 2003 1:36 pm Post subject: |
|
|
I worked out what it was. It seems if I disable "loadable module support" I get that error I don't use any modules and I have no need for module support on this machine so I normally have it disabled. Does anyone else have this problem if they disable "loadable module support"? Thanks. |
|
Back to top |
|
|
tunguska n00b
Joined: 24 Mar 2003 Posts: 6 Location: Buochs, Switzerland
|
Posted: Wed Apr 16, 2003 2:06 pm Post subject: |
|
|
LeChuck wrote: | I worked out what it was. It seems if I disable "loadable module support" I get that error I don't use any modules and I have no need for module support on this machine so I normally have it disabled. Does anyone else have this problem if they disable "loadable module support"? Thanks. |
me too! |
|
Back to top |
|
|
|