guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc-ddc


From: Jan Nieuwenhuizen
Subject: Re: gcc-ddc
Date: Thu, 23 Nov 2017 05:11:20 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Gábor Boskovits writes:

Hey Gábor,

> Jan, I can now pass the test you have in the original patch, which
> basically builds gcc-4.7.4 twice, and  checks if gcc/bin are
> identical.

Woohoo!  Amazing work!

> I'm using the getenv approach Ricardo suggested. I've not written a wrapper 
> yet, the environment variables are
> set from the build.
> As the gcc binary depends on the program name (argv[0]) we should leave it as 
> is, so the wrapper should be
> gcc-wrapper, and also gcc-ar-wrapper.
> Or something like that, and link the wrappers ot the profile as gcc, 
> gcc-ar... I think we recently had a
> discussion on that.
>
> I'd like to know if someone is willing to do this with the wrapper, or at 
> least can point me to some packages
> already doing this.
>
> I'd like some help with choosing appropriate names for these environment 
> variables.

Ricardo, ideas?

> One thing we still miss, is that the gcc-ddc package does not produce output 
> if the comparison is successful, so
> we have build failed then too.
> It would be great, if we could store the diffoscope output in a file in the 
> output directory anyway. Would you
> mind changing it that way?

That's a good idea, please do so.

> Now I changed the test to compare the full build trees, and we have several 
> files, where these same problems
> arose.
> We also have several differences coming from section .gnu_debuglink. I guess 
> that we don't need that anyway.
>
> Clone location is: https://github.com/Boskovits/guix.git
> Branch gcc-ddc.

Amazing, that's quite some work...

> I guess I will go on with this and try to make the gcc-4.7.4 build fully 
> reproducible. Once that is done we can
> try the clang one, and see if some things are still missing or not.
> We have the definition in place for that at least.

Sure.

> I cannot paste the text of the patch because of limitations in my current 
> mail client, I will work on it,
> though.
> The patch should be applied no top of the one sent by janneke.

That's fine,

Thanks
janneke

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com



reply via email to

[Prev in Thread] Current Thread [Next in Thread]