From: "Gábor Boskovits" <boskovits@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gcc-ddc
Date: Thu, 30 Nov 2017 15:32:07 +0100 [thread overview]
Message-ID: <CAE4v=pj2y-gZDjMTJg7Q2-6ej8Ld=wk53Fn=kvCy0Z4diL=r7A@mail.gmail.com> (raw)
In-Reply-To: <877eu9f56j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
It seems, that the libtool file differences leak into the checksum.
I will try to contact developers on how to bypass that issue.
2017-11-29 16:57 GMT+01:00 Jan Nieuwenhuizen <janneke@gnu.org>:
> Gábor Boskovits writes:
>
> > It seems, that I can make really good progress here.
> > Now the only things that remain:
>
> Great!
>
> > The libtool .la files record the installation directory, these are
> textfile wrappers anyways, so I don't know if
> > we should care about this.
>
> How about asking the libtool developers?
>
> > The mkheaders shell srcipt in install-tools record the installation
> directory, this is in source form by the
> > way, so I don't know if we should care about this.
>
> In a way similar to the libtool wrappers: the build is still
> reproducible in a way; just harder to check with Guix. Having
> everything below /gnu/store/deadbeef-gcc-4.7.4 identical could be a
> feature, but possibly something left for later.
>
> > The only remainig problem is that the symbol executable_checksum in cc1
> and cc1plus still differ. No other
> > differences remained.
>
> OK!
>
> > I'm now investigating the checksum issue.
>
> Great to hear your progress
> janneke
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
[-- Attachment #2: Type: text/html, Size: 2205 bytes --]
next prev parent reply other threads:[~2017-11-30 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAE4v=phLKD_nOD2CeBB26H2wDcJuwQsg1Y09BprjMg_YQq2ahw@mail.gmail.com>
2017-11-20 18:24 ` gcc-ddc Jan Nieuwenhuizen
2017-11-20 22:14 ` gcc-ddc Ricardo Wurmus
2017-11-20 23:16 ` gcc-ddc Gábor Boskovits
2017-11-21 16:36 ` gcc-ddc Gábor Boskovits
2017-11-21 16:48 ` gcc-ddc Gábor Boskovits
2017-11-21 22:01 ` gcc-ddc Jan Nieuwenhuizen
2017-11-22 14:42 ` gcc-ddc Gábor Boskovits
2017-11-23 4:11 ` gcc-ddc Jan Nieuwenhuizen
2017-11-23 7:14 ` gcc-ddc Ricardo Wurmus
2017-11-23 11:23 ` gcc-ddc Gábor Boskovits
2017-11-29 9:43 ` gcc-ddc Gábor Boskovits
2017-11-29 12:26 ` gcc-ddc Gábor Boskovits
2017-11-29 15:57 ` gcc-ddc Jan Nieuwenhuizen
2017-11-30 14:32 ` Gábor Boskovits [this message]
2017-12-01 15:44 ` gcc-ddc Gábor Boskovits
2017-12-02 14:48 ` gcc-ddc Jan Nieuwenhuizen
2017-12-02 14:53 ` gcc-ddc Gábor Boskovits
2017-12-02 22:44 ` gcc-ddc Ricardo Wurmus
2018-01-29 8:46 ` gcc-ddc Gábor Boskovits
2018-01-29 14:14 ` gcc-ddc Ludovic Courtès
2018-01-29 14:25 ` gcc-ddc Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pj2y-gZDjMTJg7Q2-6ej8Ld=wk53Fn=kvCy0Z4diL=r7A@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).