From: Chris Marusich <cmmarusich@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, bootstrappable@freelists.org
Subject: Re: diverse double compilation: using $ORIGIN?
Date: Thu, 09 Nov 2017 20:53:38 -0800 [thread overview]
Message-ID: <87bmkaray5.fsf@gmail.com> (raw)
In-Reply-To: 87wp3agd60.fsf@elephly.net
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Since the GCC build procedure is performed at least two
> times (once with the bootstrap compiler, and then again with the GCC
> variant this produces), the resulting GCC binaries should be identical.
>
> Except that they are not. One of the reasons is that the binaries
> that Guix produces embed the target output directories. This means
> that the two compiler binaries that result from diverse double
> compilation will *always* differ in at least the embedded paths, such
> as paths to itself (e.g. to binaries in the libexec directory) and
> paths to.
What ever happened to the intensional model (i.e., a content-addressed
store)? If derivation outputs were content-addressed, this would not be
a problem, right?
Dolstra's thesis presented some ideas for how to rewrite self-references
in derivation outputs under the intensional model. I've casually looked
into what happened with the intensional model since his thesis was
written, but I don't really know why it hasn't been implemented. All I
know is that Dolstra and the Nix devs seem to have moved away from that
idea; I never really learned the reason(s) why.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-11-10 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:46 diverse double compilation: using $ORIGIN? Ricardo Wurmus
2017-11-02 8:41 ` Fwd: " Ricardo Wurmus
2017-11-02 8:46 ` [bootstrappable] " Jan Nieuwenhuizen
2017-11-05 16:09 ` Ludovic Courtès
2017-11-05 16:27 ` Jan Nieuwenhuizen
2017-11-10 19:19 ` Jan Nieuwenhuizen
2017-11-05 16:11 ` Ludovic Courtès
2017-11-10 4:53 ` Chris Marusich [this message]
2017-11-11 21:56 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmkaray5.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=bootstrappable@freelists.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.