> I need to rethink what to do here, the problem is: > - if you change the .config file/the compiler/whatever you should > do: make mrproper. >
Of course. I speak about rpm -I kernel-source; cd /usr/src/linux; make modules. It is expected to work (ehh ... it is sensible to expect it :-) > - Then that looks like doing make mrproper in kernel-source (while > creating rpm) is a good idea. > > - But then you will be unable to compile modules outside of the kernel > (that is the primary reason of using modconfig in the first place). > > The only realy clean solution that I can think of is: > Right, I tend to forget it. > creating a: /usr/src/<linux_includes_for_modules-version> > and /usr/src/linux-<version> for the source package, but this is not > the more clean solution that I can think of. > No, it is even worse. Then reconfiguring kernel will invalidate module versions. They must be where they are now. > About the problem of including rhconfig.h in modsetver.h, I have to > study what to do with that. > modsetver.h already includes /boot/config.h that is not needed (here). So, there are actually two possibilities - include rhconfig.h instead (it will include /boot/config.h and do something meaningful with it) - move definition of _ver_str(x) into modsetver.h where it actually belongs. -andrej
