Summary: | x11-plugins/wmsensormon-1.2.1 fails to compile: error: sensors/chips.h: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joost Ruis <joost.ruis> |
Component: | Current packages | Assignee: | Gentoo Dockapp Team <desktop-dock> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dhp_gentoo, jeremy.william.murphy, steve-gentoo, superfastgentoo |
Priority: | High | Keywords: | PMASKED |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 301474 | ||
Attachments: | Log |
Description
Joost Ruis
2009-11-01 13:23:39 UTC
Created attachment 208941 [details]
Log
(In reply to comment #1) > Created an attachment (id=208941) [details] > Log > Which version of lm_sensors are you using? lm_sensors-3.* installs a sensors.h file with different definition/prototypes than those lm_sensors-2.10.*, the above package should have its deps on lm_sensors fixed. It builds fine against lm_snsors-2.10.8 Just updated to (as per gnome dep.) lm_sensors-3.* This left me with preserved-rebuild set and this was one of them to rebuild. (In reply to comment #3) > Just updated to (as per gnome dep.) lm_sensors-3.* > > This left me with preserved-rebuild set and this was one of them to rebuild. > That is understandable as the sonames have changed, from libsensors.so.3 to libsensors.so.4. However, the package in question seems to be dormant upstream so it will be difficult, as lot of people are moving to lm_sensors-3.* For >=2.6.31 kernels && some Moboards it is necessary to move to lm_sensors-3.* So, goodluck resolving cyclic deps!! x11-plugins/wmsensormon-1.2.1 failed to build against sys-apps/lm_sensors-3.1.1 with linux-2.6.31-xen-r10 . Logs available. Just ask. Package is broken with newer lm_sensors, upstream is unresponsive. Package.masked pending removal. How is this "FIXED" ? Keywords field should say PMASKED and resolution is "WONTFIX" *AFTER* it's been removed. *prod* When is this package actually going to be removed? (In reply to comment #8) > *prod* When is this package actually going to be removed? It takes all the time I can dedicate to it ;-) Which unfortunately is none :-( Done. |