Re: arm/aarch64 with Mes 0.23

[Vagrant Cascadian]

On 2021-05-01, Jan Nieuwenhuizen wrote:
> Vagrant Cascadian writes:

>> but I was having trouble building mes-mescc. When I pass
>> --with-bootstrap to configure, it ends with:
>>
>>   + /<<PKGBUILDDIR>>/bin/mes --no-auto-compile -e main -L
>>   /usr/share/guile/site/3.0 -C /usr/lib/guile/3.0/site-ccache /<\
>>   <PKGBUILDDIR>>/scripts/mescc.scm -- -m 32 -v -static -nostdinc -nostdlib
>>   -fno-builtin -marm -L . -static -nostdlib -o \
>>   bin/mes-mescc crt1.o gc.o hash.o lib.o math.o mes.o module.o posix.o
>>   reader.o string.o struct.o vector.o -lc
>>   mescc[mes]...
>>   error:mescc: file not found:
>>   "linux/arm-mes/elfarm-footer-single-main.hex2":()
>>   exiting...
>
> Oops.
>
>> Where's elfarm-footer-single-main.hex2 supposed to come from?
>
> It isn't ;).  It's the result of arch/bits confusion when the `-marm'
> option was added.  Also, --with-bootstrap did not learn yet about
> the new libmescc.a.  Both fixed in attached patch (and on master).

Thanks for the quick response; That indeed fixed it!

Applied the patch from master and uploaded to Debian!


>> I wasn't able to build aarc64-linux with 0.23 at all on Debian:
>>
>>   platform not supported: aarch64-linux-mes
>>   See "Porting GNU Mes" in the manual, or try --with-courage
>
> Ah, that's right, and expected.  The NEWS was a bit too optimistic here:
> in Guix we expect to use armhf-linux to bootstrap aarch64-linux, just as
> we do for x86_64-linux.

Ah, I won't bother with aarch64 on Debian yet, then.


> Thanks for testing this, and reporting it!

Always a pleasure! :)


live well,
  vagrant

signature.asc
Description: PGP signature