From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated: gnu: Add musl-cross.
Date: Sun, 3 May 2020 22:17:19 +0200 [thread overview]
Message-ID: <20200503221719.06f58042@scratchpost.org> (raw)
In-Reply-To: <87ftcgzuow.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Hi Ludo,
On Sun, 03 May 2020 21:26:23 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> I understand cross-base.scm is becoming messy and we would need an
> abstraction to facilitate its use. Still, to me it sounds like a better
> option over big monolithic packages.
>
> WDYT?
In general I'm all for using our cross toolchain mechanism.
However, this is the toolchain used by heads[1]--and they have reproducible
builds.
The use case is to be able to build heads in Guix without modification.
Their attestation of secure boot actually verifies (and asks the user and
documents the correct hashes in their README) whether the output hashes are
correct--so the toolchain doesn't need to be just similar, it needs to make
exactly the same executables.
Also, they are using musl instead of glibc. I don't think we have a musl-gcc
yet and I've never done a musl gcc before.
Could be easy, could be hard--who knows.
That said, I'm all for it.
However, I need heads for work--and one way or another it has to actually
build the official version :)
[1] https://github.com/osresearch/heads/ , basically a Linux that goes on the
BIOS flash ROM.
[2] https://github.com/osresearch/heads/pull/710
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-03 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200502155209.18737.35721@vcs0.savannah.gnu.org>
2020-05-03 19:26 ` branch master updated: gnu: Add musl-cross Ludovic Courtès
2020-05-03 20:17 ` Danny Milosavljevic [this message]
2020-05-03 20:45 ` Vincent Legoll
2020-05-06 14:01 ` 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=20200503221719.06f58042@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.