unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: Publishing an Official Statement on Self-Hosted Compilers
Date: Fri, 6 May 2016 01:30:18 +0300	[thread overview]
Message-ID: <20160505223018.GA21306@debian-netbook> (raw)
In-Reply-To: <1462459952.3184683.599099897.2F5459D9@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

On Thu, May 05, 2016 at 09:52:32AM -0500, Alex Griffin wrote:
> Hello Guixlings,
> 
> One thing I think the Guix project should do is work with the
> reproducible builds folks to publish a document explaining the issues
> involved with self-hosted compilers. It should encourage language
> communities to continuously maintain some way to build their language
> starting from hand-written C source code (or another language which can
> itself be bootstrapped from C). It could also mention that some members
> of our community are exploring ways to bootstrap gcc.
> 
> What do you think? It might be a total flop, but it looks like something
> we should try anyway! At the moment I do not see other communities
> talking about this. Guix is deeply concerned about these issues, but
> ultimately we cannot fix everything alone. If we can convince the
> Rust/OCaml/Haskell folks that this is important, we may be able to
> attract a much larger group of people to bear on the problem.
> 
> Thanks for your thoughts,
> -- 
> Alex Griffin
> 

It's not something I had really thought of before, with the focus being
on reproducable building of packages. It doesn't take much, though, to
realize that you have to start from somewhere to get reproducable and
trustable binaries. While it's easy to throw up your hands and say "its
turtles all the way down," the more the turtles rest on C's turtles the
better.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-05 22:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 14:52 Publishing an Official Statement on Self-Hosted Compilers Alex Griffin
2016-05-05 22:30 ` Efraim Flashner [this message]
2016-05-06  8:07   ` Pjotr Prins
2016-05-06  9:08 ` John Darrington
2016-05-06 10:09 ` Ludovic Courtès
2016-05-06 17:13   ` Alex Griffin
2016-05-09  8:29     ` Ludovic Courtès
2016-05-10  0:11       ` Alex Griffin
2016-05-12 10:05         ` Ludovic Courtès
2016-05-12 10:05         ` Ludovic Courtès
2016-05-21 23:22           ` Alex Griffin

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=20160505223018.GA21306@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=a@ajgrf.com \
    --cc=guix-devel@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).