Hi,
as the undefined symbols warning one gets when compiling RTAI and now
also RTnet against 2.6 started to annoy me too much, I hacked the
following lines into RTnet's configure script.
If compiling against 2.6:
if test -e $RTAI_LINUX_DIR/Module.symvers; then
mv $RTAI_LINUX_DIR/Module.symvers \
$RTAI_LINUX_DIR/Module.symvers.let_modpost_be_quiet
fi
if test -e $RTAI_LINUX_DIR/vmlinux; then
mv $RTAI_LINUX_DIR/vmlinux \
$RTAI_LINUX_DIR/vmlinux.let_modpost_be_quiet
fi
I know, this is not nice - but it works quite well :). I don't see any
practical solution for now to let the kernel's modpost know about all
external module symbols during stage 2. Maybe there is a way, but it
will then require a lot of additional work on the build concept
(separate stage 2 run over all modules like the kernel does for internal
ones?).
The lines above aren't too much intrusive in my eyes, and so they will
likely be used in RTnet for 2.6 from now on. Maybe this is also
interesting for RTAI.
Jan
