----------------- case 1: ----------------- # cat /etc/make.conf | grep CHOST CHOST="i586-pc-linux-gnu" #CHOST="i686-pc-linux-gnu" # ls /usr/lib/distcc/bin/ c++ cc g++ gcc # distcc-config --install # ls /usr/lib/distcc/bin/ c++ cc g++ gcc i586-pc-linux-gnu-c++ i586-pc-linux-gnu-g++ i586-pc-linux-gnu-gcc ----------------- ----------------- case 2: ----------------- # cat /etc/make.conf | grep CHOST #CHOST="i686-pc-linux-gnu" CHOST="i586-pc-linux-gnu" # ls /usr/lib/distcc/bin/ c++ cc g++ gcc # distcc-config --install # ls /usr/lib/distcc/bin/ c++ cc g++ gcc i686-pc-linux-gnu-c++ i686-pc-linux-gnu-g++ i686-pc-linux-gnu-gcc ----------------- This is incorrect!!!! distcc-config --install uses first CHOST value, and ignores if it is commented or not.
(In reply to comment #0) your observation is correct distcc-config is buggy in multople ways. it uses a regular expression to extract CHOST from make.conf without thinking about comments... and even if it would do so, it'd be wrong because gentoo setups where CHOST is not defined in make.conf are possible and perfectly legal. maybe using "portageq envvar CHOST" is a better way to get CHOST than that regexp in distcc-config... but now for something (not really) completely different... who will clean up the things "distcc-config --install" did upon unmerging?
I don't get why this ebuild exists; also see Bug 192741.
# Ryan Hill <dirtyepic@gentoo.org> (10 Jan 2008) # Duplicates functionality already in sys-devel/distcc # Masked for removal (treecleaner) # Bug #192741 sys-devel/distcc-config
