From: Per Jessen <per@computer.org>
To: linux-kernel@vger.kernel.org
Subject: building 2.4.31 for a non-smp system
Date: Sat, 29 Oct 2005 10:47:29 +0200 [thread overview]
Message-ID: <43633721.9010001@computer.org> (raw)
I'm upgrading a box from 2.4.23 to .31, but I'm seeing lots of errors
along these lines:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-nostdinc -iwithprefix include -DKBUILD_BASENAME=tty_ioctl
-DEXPORT_SYMTAB -c tty_ioctl.c
In file included from /usr/src/linux-2.4.31/include/linux
modversions.h:177,
from /usr/src/linux-2.4.31/include/linux/module.h:22,
from tty_ioctl.c:21:
/usr/src/linux-2.4.31/include/linux/modules/ksyms.ver:576:1: warning:
"del_timer_sync" redefined
In file included from /usr/src/linux-2.4.31/include/linux
ext3_fs_sb.h:20,
from /usr/src/linux-2.4.31/include/linux/fs.h:715,
from /usr/src/linux-2.4.31/include/linux
capability.h:17,
from /usr/src/linux-2.4.31/include/linux/binfmts.h:5,
from /usr/src/linux-2.4.31/include/linux/sched.h:9,
from tty_ioctl.c:14:
/usr/src/linux-2.4.31/include/linux/timer.h:30:1: warning: this is the
location of the previous definition
In file included from /usr/src/linux-2.4.31/include/linux
modversions.h:177,
from /usr/src/linux-2.4.31/include/linux/module.h:22,
from tty_ioctl.c:21:
/usr/src/linux-2.4.31/include/linux/modules/ksyms.ver:660:1: warning:
"set_cpus_allowed" redefined
In file included from tty_ioctl.c:14:
/usr/src/linux-2.4.31/include/linux/sched.h:159:1: warning: this is the
location of the previous definition
The redefinition of "set_cpus_allowed" and "del_timer_sync" only happen
when CONFIG_SMP isn't set.
I guess I could simply compile with CONFIG_SMP, but surely something's
not right here?
Follow-up:
OK, I've built the kernel with SMP support, and I'm not seeing the above
any longer. However, when I tried to load module nfsd, I get:
/lib/modules/2.4.31/kernel/net/sunrpc/sunrpc.o: unresolved symbol
kernel_flag_cacheline
/lib/modules/2.4.31/kernel/net/sunrpc/sunrpc.o: unresolved symbol
atomic_dec_and_lock
/lib/modules/2.4.31/kernel/net/sunrpc/sunrpc.o: insmod
/lib/modules/2.4.31/kernel/net/sunrpc/sunrpc.o failed
/lib/modules/2.4.31/kernel/net/sunrpc/sunrpc.o: insmod nfsd failed
Per Jessen, Zurich
next reply other threads:[~2005-10-29 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 8:47 Per Jessen [this message]
2005-10-29 11:00 ` building 2.4.31 for a non-smp system Adrian Bunk
[not found] <20051029112755.C6F8B9801D@mail.local.net>
2005-10-29 11:34 ` Per Jessen
2005-10-29 11:57 ` Per Jessen
2005-10-29 12:04 ` Willy Tarreau
2005-10-29 14:53 ` Gene Heskett
2005-10-29 12:18 ` Adrian Bunk
2005-10-29 13:58 ` Per Jessen
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=43633721.9010001@computer.org \
--to=per@computer.org \
--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 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.