2.6.4: strange (?) include path order

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

 



> > Did you install i2c-2.6.4 before lm_sensors-2.6.4? My guess is, you
> > didn't.
> Of course I didn't:
> I'm using 2.4.18 builtin i2c support modules.
> If you don't plan to/can't fix this, then maybe you might want to
> mention this in the FAQ...

I don't see how we could fix this. If we have /usr/src/linux/include
before /usr/local/include, people installing the latest i2c release
won't see it used and will probably get somehow frustrated. What's more,
I think it is always better to use the version of i2c we release with
lm_sensors. Of course, older versions (and thus kernel version) may
work, but it may not work as well.
Now, is it worth an entry in the FAQ? Not even sure. I think (I indeed
*hope*) that someone encountering the problem you faced would try
updating i2c before reading the FAQ (and so, wouldn't read the FAQ since
it would work). Anyone got a different opinion?

> Currently having a look at the perl script detection code...
> Hmm, weird stuff. Not sure yet what can be done about that.

I don't get you. What do you mean?

-- 
Jean "Khali" 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