Wouter Verhelst <[EMAIL PROTECTED]> writes:
> On Mon, Feb 21, 2005 at 12:09:16AM -0300, Henrique de Moraes Holschuh wrote:
>> On Sun, 20 Feb 2005, Brian Nelson wrote:
>> > Also, really huge stuff, like KDE, cannot be uploaded as frequently
>> > as perhaps the maintainers would like because it kills the slower
>> > buildd's for a few days.
>>
>> The answer to that is to setup a dist-cc cluster for these archs,
>> where only the master node is in the slow arch, and everything else is
>> a fast arch.
>
> That would require cross-compilers on the other hosts in the distcc
> cluster, and (unless I don't understand how dist-cc works; never had a
> look at it) a mechanism to install build-dependencies on those hosts in
> addition to the one on the 'slow' node.
Actualy I think dist-cc requires a cross-gcc on the other nodes and
then sends the preprocessed C/C++ source to those nodes and the binary
objects back. All the configure tests, linking and testcases would be
done on the real host.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
