Re: DMODVERSIONS causing a lot of problems
>Would someone kindly clarify the aspects of the DMODVERSIONS flag in
>the kernel makefile?
It inserts versioning symbols into modules so that you can (possibly)
run them in kernels other than that which they were compiled against.
However, I don't think this is really your problem - it was just the
first thing to die.
>After not getting the aureal sound driver to install, I'm so unsure
>about enabling or disabling this feature the next time I have to build
>a new kernel. Most astonishing is the first output of make:
>make install AUCHIP=AU8820
>make: Entering directory `/root/drivers/sound/aureal'
>cc -D__KERNEL__ -DMODULE -DAU8820 -mpentium -O6 -fomit-frame-pointer
>-Wall -pipe -I/usr/src/linux/include -c -o au_audio.o au_audio.c
>In file included from au_audio.c:49:
>au_vortex.h:55: linux/modversions.h: No such file or directory
>Where does the routine look for the header,
Wherever the C compiler is looking for include files; specifically,
I've underlined two paths above which ought to be in similar places but
aren't. Are you doing something odd with symlinks?
Also, you really shouldn't be building kernels as root if you can avoid
it. Only the installation step requires root access, so keeping kernels
in /root - and keeping them in /root itself rather than a subdirectory
such as /root/linux is even odder! - is usually not the thing to do.
I'd like, if possible, to see the commands you're issuing before running
'make install', and what directory you're in when you run them. Also,
note that when you change configuration options you may well have to run
>Then, some people recommended to exclude DMODVERSIONS out of .config -
>some (which?) apps would not need this option. This is really a maze.
No, you shouldn't have to do that. Again, I don't think -DMODVERSIONS is
the direct cause of the problem you're experiencing.
Colin Watson [email@example.com]