From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Cc: Danny Milosavljevic <dannym@scratchpost.org>
Subject: Re: GNU Mes 0.24.1 released
Date: Wed, 19 Oct 2022 21:41:20 +0200 [thread overview]
Message-ID: <87czanha8v.fsf@gnu.org> (raw)
In-Reply-To: <87czanj0cn.fsf@gnu.org>
Ludovic Courtès writes:
Hey!
> Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
>
> This is exciting news! Looking forward to having full-source
> bootstrapped AArch64… and it looks like there’s already activity on a
> ‘wip-’ branch.
Yes, it is! The ARM bootstrap story is still a bit flakey, as
stage0-posix does not support ARM. So, ARM would need
%bootstrap-mescc-tools and %bootstrap-mes binary seeds...meh.
However, aarch64-linux now bootstraps from 526 bytes all the way until
gcc-core-mesboot 2,95.3. Very nice!
We're still stuck at building a full gcc+glibc combo;
glibc-mesboot-2.2.5 builds, but possibly not correctly; as the full
gcc-mesboot0 (2.95.3) build fails at configure time: gcc-core-mesboot0 +
glibc-mesboot0
?: 0 [execle "./gencheck" # "./gencheck"]
ERROR: In procedure execle: Exec format error
Not sure what to do here. We could somehow try to debug/bisect this.
We could try to use a newer glibc; glibc-2.2.5 happened during the
OABI/EABI switch and is heavily patched. Or, we could try to remove
glibc-2.2.5/gcc-2.95.3 altogether and aim for a direct tcc => gcc-4.6.4.
We need to go that way anyway for RISCV.
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
next prev parent reply other threads:[~2022-10-19 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 8:59 GNU Mes 0.24.1 released Janneke Nieuwenhuizen
2022-10-19 15:32 ` Ludovic Courtès
2022-10-19 19:41 ` Janneke Nieuwenhuizen [this message]
2022-10-19 19:57 ` Efraim Flashner
2022-10-20 14:11 ` Jan Nieuwenhuizen
2022-10-20 13:13 ` Ludovic Courtès
2022-10-22 18:02 ` Efraim Flashner
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=87czanha8v.fsf@gnu.org \
--to=janneke@gnu.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.