> I know all of that and I've already set up the distccd on the local host > in this way (not via distcc_hosts but by configuring distccd on > localhost). BUT, for some reason portage does _not_ use distcc at all > but the "normal" gcc and this will result in -jN jobs running on > localhost.
Phil, I've noticed the same lack of distcc usage that you've encountered. I haven't isolated the cause (i.e. I think portage has been updated twice since it started to fail for me), but I can assure you that it's not necessarily anything you're doing... -- [email protected] mailing list
