all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	guix-devel@gnu.org,
	"Danny Milosavljevic" <dannym@scratchpost.org>
Subject: Re: GNU Mes 0.24.1 released
Date: Wed, 19 Oct 2022 22:57:20 +0300	[thread overview]
Message-ID: <Y1BWoDJzdyKe6nTK@3900XT> (raw)
In-Reply-To: <87czanha8v.fsf@gnu.org>

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

On Wed, Oct 19, 2022 at 09:41:20PM +0200, Janneke Nieuwenhuizen wrote:
> 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.

Which hardware are you building on? On my pine64 I'm getting stuck at
tcc-0.9.26-1134-g80114c4d
On commit 519f4c8c9a0b191e9a447116685393c2fed4cd3b

starting phase `build'
  CC         tccpp.c
->type--: not a <type>: (typename "BufferedFile")
->type--: not a <type>: (typename "BufferedFile")
  CC         tccgen.c
  CC         tccelf.c
unexpected size:8
rank--: not a pointer: #<<type> type: signed size: 1 description: #f>
rank--: not a pointer: #<<type> type: signed size: 1 description: #f>
  CC         tccrun.c
  CC         arm-gen.c
unexpected size:8
  CC         arm-link.c
  CC         arm-asm.c
  CC         tccasm.c
  CC         libtcc.c
  CC         tcc.c
  CCLD       mes-tcc
mkdir -p /gnu/store/d3kcgm0z3yyc7bplaacr7g0j8gk36h5j-tcc-boot0-0.9.26-1134-g80114c4d/lib/tcc
rm -f crt1.o;
cp -f /gnu/store/nli76zd955d9xksy01qrfzlizq4c28kd-mes-boot-0.24.1//lib/crt1.c .
crt1.c:149: warning: implicit declaration of function 'main'
rm -f crti.o;
cp -f /gnu/store/nli76zd955d9xksy01qrfzlizq4c28kd-mes-boot-0.24.1//lib/crti.c .
rm -f crtn.o;
cp -f /gnu/store/nli76zd955d9xksy01qrfzlizq4c28kd-mes-boot-0.24.1//lib/crtn.c .
rm -f libc.a
cp -f /gnu/store/nli76zd955d9xksy01qrfzlizq4c28kd-mes-boot-0.24.1//lib/libc+gnu.c libc.c
error: in phase 'build': uncaught exception:
srfi-34 #<condition &invoke-error [program: "sh" arguments: ("bootstrap.sh") exit-status: 1 term-signal: #f stop-signal: #f] 10f6100>
phase `build' failed after 21994.9 seconds


-- 
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: 833 bytes --]

  reply	other threads:[~2022-10-19 19:58 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
2022-10-19 19:57     ` Efraim Flashner [this message]
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=Y1BWoDJzdyKe6nTK@3900XT \
    --to=efraim@flashner.co.il \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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.