It actually doesnt stop distcc - just runs a single make job on the other machine. Very useful for low powered machines as you dont specify "localhost" so all the makes are remote, even if just one machine (should be, doesnt always happen tho!)
To stop distcc use "FEATURES="-distcc" However, this thread is of use to me as I also have a laptop that plain refuses to distcc anything. Havent had time trace it yet, but the symptoms are similar to what others are reporting. Only difference with my usual inastall method is that I tried to set up distcc according to the gentoo guide so it would be used during bootstrap - it didnt work there either. Think were looking at some kind of configuration bug that some systems trigger? BillK On Fri, 2005-02-04 at 11:55 +1300, Nick Rout wrote: > On Thu, 03 Feb 2005 23:27:59 +0100 > Philip Lawatsch <[EMAIL PROTECTED]> wrote: > > > Also I doubt that a package can "disable" distcc if it does not use > > something advanced to check for the real gcc. If you just disable > > parallel make you wont automagically stop distcc from being used afair. > > Yes I guess that is true, but then how do you know distcc is being used with > -j1, with the -j1 being set by the package (or perhaps the ebuild). An ebuild > could also presumably over ride FEATURES > -- William Kenworthy <[EMAIL PROTECTED]> Home! -- gentoo-user@gentoo.org mailing list
