+++ This bug was initially created as a clone of Bug #186635 +++ During the compile phase for slocate (version 3.1-r2), cc is invoked instead of a CHOST-specific command (like i686-pc-linux-gnu-gcc). This could cause troubles if trying to do, say, a cross-compile and the system cc gets called (since normally it would use the CHOST for the cross compiler). >>> Compiling source in /var/tmp/portage/sys-apps/slocate-3.1-r2/work/slocate-3.1 ... make -C src make: Entering directory `/var/tmp/portage/sys-apps/slocate-3.1-r2/work/slocate-3.1/src' cc -c -march=core2 -mtune=generic -O2 -pipe -fomit-frame-pointer -Wall -Wshadow -o slocate.o slocate.c cc -c -march=core2 -mtune=generic -O2 -pipe -fomit-frame-pointer -Wall -Wshadow -o cmds.o cmds.c cc -c -march=core2 -mtune=generic -O2 -pipe -fomit-frame-pointer -Wall -Wshadow -o conf.o conf.c cc -c -march=core2 -mtune=generic -O2 -pipe -fomit-frame-pointer -Wall -Wshadow -o utils.o utils.c cc -march=core2 -mtune=generic -O2 -pipe -fomit-frame-pointer -Wall -Wshadow -Wl,-O1 -o slocate slocate.o cmds.o conf.o utils.o Reproducible: Always Steps to Reproduce: 1. Install bdelta 2. Look at output during compile phase 3. Actual Results: cc is invoked Expected Results: A CHOST-specific compiler name to be invoked
Created attachment 200656 [details] diff between original and fixed ebuild
thanks, fixed in cvs http://sources.gentoo.org/sys-apps/slocate/slocate-3.1-r2.ebuild?r1=1.1&r2=1.2
