Created attachment 275883 [details]
This bug is being reported because this ebuild is currently trying to build against the kernel tree by accessing it through /lib/modules/`uname -r` instead than through /usr/src/linux like it should.
This is bad in many situations, like:
- livecd installs: the running kernel is the one from the livecd and is most
likely not the same the user is installing to;
- livecd chroot fixes: as above;
- generic chroot: running kernel comes from outside, as above;
- kernel updates: users most likely would w
If this is an automated QA check, then I'm not sure it's what it thinks it is... The use of uname is to sed the package Makefile with the correct values from the eclass; if there's a better way, please enlighten...
(In reply to comment #1)
> If this is an automated QA check, then I'm not sure it's what it thinks it
> is... The use of uname is to sed the package Makefile with the correct
> values from the eclass; if there's a better way, please enlighten...
no longer in portage, package removed due to this bug and additional reasons like not being compatible with current linux-headers, like eg. 3.8, 3.9, 3.10, ...