Re: 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]))

2005-02-22 Thread Thiemo Seufer
Petri Latvala wrote: [snip] > Also, the first 16 bytes will differ in an ELF format .o, see > http://lists.debian.org/debian-devel/2004/09/msg00201.html That's incorrect, strictly speaking. The first (magic) bytes have to be identical, only the padding bytes could be different (but are usually zer

Re: 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]))

2005-02-22 Thread Petri Latvala
On Wed, Feb 23, 2005 at 12:38:46AM +1100, Paul Hampson wrote: > 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? -frandom-s

Re: Cross-compiling and dist-cc

2005-02-22 Thread Thomas Bushnell BSG
John Hasler <[EMAIL PROTECTED]> writes: > Wouter Verhelst wrote: > > 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... > > The idea is to cr

Re: 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]))

2005-02-22 Thread Thomas Bushnell BSG
[EMAIL PROTECTED] (Paul Hampson) writes: > Or have I missed something important? Yes. There are a jillion different machine code programs that do the same thing and a compiler could generate any one of them in response to the same source. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a s

Re: Cross-compiling and dist-cc

2005-02-22 Thread Tollef Fog Heen
* Will Newton | A suprising number of programs embed the current date, time, hostname etc. in | their user visible version strings. The Linux kernel for example, does not | compile identically twice unless you hack it slightly. Even with the same preprocessed source? -- Tollef Fog Heen

Re: Cross-compiling and dist-cc

2005-02-22 Thread Will Newton
On Tuesday 22 February 2005 14:01, John Hasler wrote: > Wouter Verhelst wrote: > > 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... > > The i

Re: Cross-compiling and dist-cc

2005-02-22 Thread John Hasler
Wouter Verhelst wrote: > 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... The idea is to cross-compile and native-compile _for_ _the_ _same_ _ta

Re: 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]))

2005-02-22 Thread Thiemo Seufer
Paul Hampson wrote: > 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

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]))

2005-02-22 Thread 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