Paul paul.corner@tesco.net writes:
Question though - Is there an easy way of finding out what symbols are causing the error messages reported by depmod ?
I think there's a -v option to depmod which gets you the full list of symbols. However, the usual cause of such problems is because you installed two kernels with the same modules directory simultaneously. For this reason, when building my own kernel packages, I tend to add a suffix (EXTRAVERSION I think the Makefile directive is) to the version. Debian don't do that, so I avoid conflicting.
depmod -v appears to list all the symbols of each module visited. Unfortunately, it still doesn't tel me which ones are unresolved - Or maybe it does, and I don't know how to decipher the info.
I currently have about five different kernels on this machine, 2.2.18-rtx through to 2.4.9-bifino - That really screws up any C source that depends on specific kernel version info to build correctly <g>
Regards, Paul.
On Monday 24 September 2001 10:03 am, MJ Ray wrote:
I think there's a -v option to depmod which gets you the full list of symbols. However, the usual cause of such problems is because you installed two kernels with the same modules directory simultaneously. For this reason, when building my own kernel packages, I tend to add a suffix (EXTRAVERSION I think the Makefile directive is) to the version. Debian don't do that, so I avoid conflicting.
-
MJ Ray -
Paul