Wendy Elmer <[email protected]> writes: > On Thu, 2009-06-18 at 13:36 -0700, Russ Allbery wrote:
>> How are you building the kernel modules? Is it possible that you had >> an old build in the same source tree that wasn't fully cleaned, or >> that might have reused configure results from an earlier kernel? (If >> you're using module-assistant, it's particularly bad about this. You >> have to run module-assistant clean <module> before building against a >> new kernel or you'll get unpredictable results.) > I may have had an old openafs in my modules directory, I'm not sure. > It could be that I installed openafs source but hadn't untarred it > into my modules directory. I build by using make-kpkg with > kernel-image modules-image. I always do a make-kpkg clean before. An old openafs module would have done it, since there's a workaround that's detected at configure time. Old source might have caused this problem, but only if it was fairly old. If you run into this again and can't find an old module or old source that's botching things up, let me know. It really shouldn't happen unless configure options that you're not using are enabled. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
