unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, bug-mes@gnu.org
Subject: Re: wip-arm-bootstrap: Reduced binary seed bootstrap
Date: Tue, 22 Dec 2020 16:10:46 +0100	[thread overview]
Message-ID: <87v9ctzxjd.fsf@gnu.org> (raw)
In-Reply-To: <87ft40vevv.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sun, 20 Dec 2020 13:30:28 +0100")

Hello!

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> I pushed an initial wip-arm-bootstrap that builds up to tcc-boot:
>
> ./pre-inst-env guix build -e '(@@ (gnu packages commencement) tcc-boot)'
>
>
> Danny did a terrific job on armhf-linux support for GNU Mes and we are
> getting close to release v0.23.  What's known to be missing is "setjmp"
> support for tcc/gcc.  And, of course, for the Reduced binary seed
> bootstrap to work on ARM!

Woohoo, thumbs up for this great milestone, hackers! 🎉

> Anyway, the problem I'm looking at now is that while tcc-boot builds on
> an ARM box, it does not build on aarch64-linux, i.e. this
>
> ./pre-inst-env guix build --system=armhf-linux \
>   -e '(@@ (gnu packages commencement) tcc-boot0)'
>
> fails on overdrive1.

That’s “interesting”.  Did you eventually find a lead?

>   configure: error: 'mescc' failed to compile conftest.c.
> Backtrace:
> In unknown file:
>    ?: 19 [apply-smob/1 #<catch-closure 410f30>]
> [..]
> In gash/shell.scm:
>  165: 1 [sh:exec-let () "./conftest" "triplet"]
> In unknown file:
>    ?: 0 [execle "./conftest" # "./conftest" ...]
>
> ERROR: In procedure execle:
> ERROR: In procedure execle: No such file or directory

Looks like the ELF interpreter on ‘conftest’ might be wrong?

Thanks for the update, it’s exciting!

Ludo’.


  parent reply	other threads:[~2020-12-22 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 12:30 wip-arm-bootstrap: Reduced binary seed bootstrap Jan Nieuwenhuizen
2020-12-21 10:10 ` Jan Nieuwenhuizen
2020-12-22 15:10 ` Ludovic Courtès [this message]
2020-12-23 12:14   ` Jan Nieuwenhuizen

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=87v9ctzxjd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-mes@gnu.org \
    --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).