2.7.0 testings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I see. Well, MODPREF controls where the modules get installed.
> That should be the same as the kernel that we compiled against,
> which is the one defined in LINUX:= .
> So don't you think MODPREF should do the "-L" thing?
> But I don't know what happens if we default to /usr/src/linux...

If we default to /usr/src/linux, it means that we don't use the release
of the currently running version of Linux. So, KERNELVERSION is useless.
The only way we have to know where the modules should be installed is to
look in /usr/src/linux and see where this kernel has installed its
modules. This is exactly what is done right now.

If we didn't default to /usr/src/linux, it means that we know where to
install the modules, and we could use KERNELVERSION. But, on the other
hand, we built LINUX from KERNELVERSION (through the build symlink), so
the method above will also work.

I don't see the point in creating a complex expression that does
different things for these two cases when the first one will work for
both (and has obviously proven to work well for years).

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux