Cross-compiling and dist-cc (Was: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space]))

[Paul.Hampson@anu.edu.au (Paul Hampson)]

On Tue, Feb 22, 2005 at 12:44:27PM +0100, Wouter Verhelst wrote:
> On Tue, Feb 22, 2005 at 08:48:48PM +1300, Nick Phillips wrote:
> > Running such a system in parallel with the current systems (and comparing
> > the outputs) might be a good test for gcc-as-cross-compiler, then...

> And a hell of a lot of work. You can't just create checksums of the
> resulting binaries and compare those; it's not as if any difference
> between the two compiled binaries would constitute an error...

Why not? Is there something non-deterministic in the compilation
process?

Ideally, version x of gcc should produce the same output natively
as when cross-compiling.

Or have I missed something important?

(I'm actually quite fond of the idea of dist-cc sending pre-processed
C code to remote (faster) machines and getting unlinked object code
back. I haven't got a good use for it yet, but the _idea_ is neat.)

-- 
-----------------------------------------------------------
Paul "TBBle" Hampson, MCSE
8th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Anu.edu.au

"No survivors? Then where do the stories come from I wonder?"
-- Capt. Jack Sparrow, "Pirates of the Caribbean"

This email is licensed to the recipient for non-commercial
use, duplication and distribution.
-----------------------------------------------------------

Attachment: signature.asc
Description: Digital signature