read the bug :) - the bug numbers in the email, or search the forums like I did.
Are you sure its building? distcc connects to the machine in question, but doesnt actually build anything as it cant run gcc as the toolchain does not call it gcc internally anymore, but includes i[3456]86 in the naming scheme. So if you are crossing one of these boundaries (i.e., trying o build for a K6 which is i586 using a later pentium which is i686), it wont work. I see I was wrong in citing athlon/pentium as they are both i686 - that being said my athlon pentium combination is not working at the moment, which I will have to look into again soon. BillK On Fri, 2005-06-17 at 09:04 -0400, Dave Nebinger wrote: > > There were some changes to the tool chain which means that distcc wont > > work across different x86 archs (e.g., athlon and pentium) and the devs > > wont change it (marked as WONT FIX on the bug). > > Hmm, I haven't heard anything about this and have been using distcc on an > x86 & athlon network. Each host seems to be doing the write thing as all of > the machines are recently sync'd and built. > > What exactly were the nature of the changes and how does this introduce a > bug? > > Also if it is truly a bug, why does the handbook still include the > references to building using distcc? Wouldn't failures in distcc lead to > more installation problems? The apparent stability of a gentoo-based system > would then be subject to question, not something I'd like to see happen... > > > -- William Kenworthy <[EMAIL PROTECTED]> Home! -- gentoo-user@gentoo.org mailing list
