#include <hallo.h>
* Roberto C. Sanchez [Tue, Aug 30 2005, 01:06:39AM]:
> > Why?
> >
> Becuase I roll my own kernel. If I upgrade the kernel with gcc-3.3
> (currently the Sarge default) and then upgrade to Etch (which will have
> gcc-4.0 for a default) I will run into problems if I decide to add new
> modules to my kernel. Thus, those with a self-compiled kernel are in a
The compiler <-> kernel has "always" been there and has nothing to do
with udev (or any other kernel-stuff-in-userspace troublemaker of the
day).
For modules, you need to know what you are doing. Unfortunately the
kernel developers seem to be ignorant WRT such things, "gcc" is
hardcoded in assumption of beeing a never changing compatibility
constant.
For additional modules packages using module-assistant there is a
workaround that will push the right compiler into the path, but that is
a cludge. It will fail with "other" module packages that just rely on
the kernel build system and it will fail if you try to build some
extra kernel modules without rebuilding the whole kernel and without
manually forcing the kernel build system to use the correct gcc.
Regards,
Eduard.
--
Wo haben wir denn das Dingens mit dem Dingens?
-- Torsten Spindler
