Issue: sys-boot/lilo-24.2 calls cc directly.
Discovered on: amd64 (internal ref: ci)
As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks] and set the CC variable to x86_64-pc-linux-gnu-gcc.
Created attachment 670511 [details]
build log and emerge --info
it uses the right CC while the check picks the wrong one
(In reply to Agostino Sarubbo from comment #2)
> it uses the right CC while the check picks the wrong one
Is the check in lilo itself or is this something the ebuild is doing wrong?