| Summary: | kdebase-3.5.9-r3 builds ksysguard without lm_sensor support | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Johannes Niess <johannes_niess> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kinkitzu |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Johannes Niess
2008-05-27 17:19:00 UTC
As seen at http://bugs.kde.org/show_bug.cgi?id=158487 and my own observations, it appears that the config.h.in file (and therefore config.h file) is generated wrong, but I can't figure out how config.h.in is generated. Frans Pop noticed that the differences of 3.5.8->9 ksysguard/ksysguardd/Linux/lmsensors.c is the following: -#ifdef HAVE_SENSORS_SENSORS_H +#ifdef HAVE_LMSENSORS When you look in work/ksysguard-3.5.9/config.h.in file during compilation, there is: #undef HAVE_SENSORS_SENSORS_H Which I fixed by just editing mid-compilation and changing to: #define HAVE_LMSENSORS 1 Naturally, a hackjob like that isn't very satisfactory as a fix, but if someone could either fix this or let me know how automake works so I could have a crack at it, that would be choice. Fixed in CVS in kdebase-3.5.9-r4 and ksysguard-3.5.9-r1, thanks for reporting. kdebase-3.5.9-r4 fixes it for me. Thank you very much. Creating new lmsensor plots is required. Existing lmsensor plots still display thunderbolt icon and no sensor reading. Cause could be a name change on sensors. |