From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: gcc-ddc Date: Thu, 23 Nov 2017 05:11:20 +0100 Message-ID: <87d149hbx3.fsf@gnu.org> References: <871skskduj.fsf@gnu.org> <87lgj0wqbd.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eHirR-0005GR-FR for guix-devel@gnu.org; Wed, 22 Nov 2017 23:11:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eHirO-00040y-A5 for guix-devel@gnu.org; Wed, 22 Nov 2017 23:11:37 -0500 In-Reply-To: (=?utf-8?Q?=22G=C3=A1bor?= Boskovits"'s message of "Wed, 22 Nov 2017 15:42:28 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: Guix-devel G=C3=A1bor Boskovits writes: Hey G=C3=A1bor, > Jan, I can now pass the test you have in the original patch, which > basically builds gcc-4.7.4 twice, and=C2=A0 checks if gcc/bin are > identical. Woohoo! Amazing work! > I'm using the getenv approach Ricardo suggested. I've not written a wrapp= er yet, the environment variables are > set from the build. > As the gcc binary depends on the program name (argv[0]) we should leave i= t 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 out= put 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 t= he 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 sever= al files, where these same problems > arose. > We also have several differences coming from section .gnu_debuglink. I gu= ess that we don't need that anyway. > > Clone location is:=C2=A0https://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 --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com