Re: Error building lm-sensors (can't find i2c headers) - More info
:: David Z Maze writes:
Hello!
> Phew. Let's see...
JP> KSRC:=/usr/src/linux
JP> MODULE_LOC:=/usr/src/modules
> Can you try locally changing the second line to
> 'MODULE_LOC?=/usr/src/modules'? If that works, I can make the change
> in the package, too.
Yes, that works! I wonder why the behavior was different for KSRC and
MODULE_LOC...
JP> Because it is loking for headers in the i2c dir, and not in i2c/linux,
JP> and I'd expect (that's where the headers are).
> No, that doesn't seem right; it's looking for <linux/i2c-proc.h> under
> $(MODULE_LOC)/i2c, so if you concatenate these two pieces in the
> correct order, you should find the header file.
Ah, right! Silly me! :-)
> It looks like what's actually happening here is that the
> dependency-detecting code[1] is losing. Does running 'make clean'
> before trying the build fix this? (Should probably add a comment to
> README.Debian about this, since it seems a not-too-infrequent failure
> mode.) (And I checked, the .d files aren't included in the source
> tarball.)
Yes, that fixed it! Thank you a lot! Now I got all the module packages!
Just modprobe'd the modules, and they're working fine. :-)
Maybe the kdist target could call clean before building (and not only
after doing it)? Of course, then the whole compilation process would
be repeated every time one called make kdist...
JP> What's going on? I feel like I missed something really basic and I
JP> shouldn't need to change the rules script, but things don't seem to
JP> work here...
> Errm, yeah, it's pretty clear that there's a bug with
> not-in-the-default-place module building. :-(
Oh, well... Maybe just changing the lines that assign values to those
2 vars and including clean before the build would fix things?
Thanks a lot for the help!
J.
--
Reply to: