Re: GNU Mes 0.24.1 released
On Wed, Oct 19, 2022 at 09:41:20PM +0200, Janneke Nieuwenhuizen wrote: > Ludovic Courtès writes: > > Hey! > > > Janneke Nieuwenhuizen 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. I noticed that when offloading from my x86_64 box to my aarch64 machine target gets (%current-system) from the originating system, not from the system doing the building. I'm testing moving the '(let ((triplet ...' code down from the top of the definition to inside the arguments. I didn't see a difference with 'guix build -d' for x86_64 from x86_64, but the derivation did change with the planned offload to an aarch64 machine. I looked into gcc-2.95 more than I wanted to last week with GHC-4.08, would it help if we specified we wanted armv4 or armv4t or strongswan instead of "generic"? -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: GNU Mes 0.24.1 released
Hi, Janneke Nieuwenhuizen skribis: >> Janneke Nieuwenhuizen 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. By “ARM”, you mean the 32-bit ARMv7 ISA, which armhf-linux targets, right? (AArch64, aka. ARMv8, is also “ARM”. :-)) > However, aarch64-linux now bootstraps from 526 bytes all the way until > gcc-core-mesboot 2,95.3. Very nice! Impressive! > 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. This issue is on aarch64-linux? What does “file gencheck” say? > 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. That sounds like the best approach longer-term, but possibly more work than figuring out the issue above? Thanks, Ludo’.
Re: GNU Mes 0.24.1 released
Efraim Flashner writes: Hi Efraim, > On Wed, Oct 19, 2022 at 09:41:20PM +0200, Janneke Nieuwenhuizen wrote: > > 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' > 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 # exit-status: 1 term-signal: #f stop-signal: #f] 10f6100> > phase `build' failed after 21994.9 seconds Oops. Not sure what happened on my side, but yeah this error reproduces for me. I've pushed an updated tcc-boot0 to wip-aarch64-bootstrap. Greetings, Janneke -- Jan Nieuwenhuizen | GNU LilyPond https://lilypond.org Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com
Re: GNU Mes 0.24.1 released
On Wed, Oct 19, 2022 at 09:41:20PM +0200, Janneke Nieuwenhuizen wrote: > Ludovic Courtès writes: > > Hey! > > > Janneke Nieuwenhuizen 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 : (typename "BufferedFile") ->type--: not a : (typename "BufferedFile") CC tccgen.c CC tccelf.c unexpected size:8 rank--: not a pointer: #< type: signed size: 1 description: #f> rank--: not a pointer: #< 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 # phase `build' failed after 21994.9 seconds -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: GNU Mes 0.24.1 released
Ludovic Courtès writes: Hey! > Janneke Nieuwenhuizen 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 | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
Re: GNU Mes 0.24.1 released
Howdy, Janneke Nieuwenhuizen skribis: > We are happy to announce the release of GNU Mes 0.24.1, representing 23 > commits over five months by four people. > > Mes now supports the stage0-posix and M2-Planet Full Source bootstrap on > Aarch64 for ARM. Because stage0-posix does not support ARM yet, the Mes > ARM bootstrap is currently prototyped on Aarch64. This is exciting news! Looking forward to having full-source bootstrapped AArch64… and it looks like there’s already activity on a ‘wip-’ branch. Cheers, Ludo’.
