sys-apps/lm_sensors-3.2.0 and -3.3.0 needs build time depenencies on sys-devel/bison and sys-devel/flex. On x86 they are not part of @system. Reproducible: Always Steps to Reproduce: 1. emerge -C bison flex 2. emerge sys-apps/lm_sensors-3.2.0 or -3.3.0 Actual Results: Compilation without bison fails with sed -e 's@^\(.*\)\.o:@prog/sensors/main.rd prog/sensors/main.ro: Makefile '`dirname prog/sensors/main.rd`/Module.mk' @' > prog/sensors/main.rd Please install bison, then run "make clean" and try again make: *** [lib/conf-parse.c] Error 1 Compilation with bison but no flex fails with sed -e 's@^\(.*\)\.o:@lib/data.ld lib/data.lo: Makefile '`dirname lib/data.ld`/Module.mk' @' > lib/data.ld flex -Psensors_yy -t -Cfe -8 lib/conf-lex.l > lib/conf-lex.c /bin/sh: flex: command not found make: *** [lib/conf-lex.c] Error 127 "emerge bison flex lm-sensors" fixes the issue
Fixed for 3.3.0, which will go stable now in another bug.
Seriously? Let's just add flex and bison to 3.3.0 and wait for someone else to report that 3.2.0 is broken? Bug 382899.
Yes, a version 3.2.0-r1 would have been nice. I am installing my little sister's PC, and a long emerge of some 900 packages that I started this night stopped right after I went to bed, because of this bug. So she will have to wait for another day until it is finished. Just my opinion. I don't want to piss any dev off or sound harsh, just saying that this bug that has been 'fixed' five months ago still makes trouble. And I suppose most people have bison installed already, but when you're doing a fresh install, this is not the case, and having this happen is especially annoying then as it stops the whole process because some kde-related stuff seems to depend on lm_sensors.
