IRC channel logs

2021-04-25.log

back to list of logs

<vagrantc>should mes build on arm v5? https://buildd.debian.org/status/package.php?p=mes&suite=experimental
<vagrantc>or is arm v7 a reasonable minimum?
<vagrantc>i guess you want it to bootstrap on anything in the end ...
<vagrantc>stage0_cpu=armv7l
<vagrantc>that's telling
<vagrantc>ok, i'll drop armel (arm v5) from supported architectures on debian
<vagrantc>where's linux/arm-mes/elfarm-footer-single-main.hex2 come from?
<vagrantc>error:mescc: file not found: "linux/arm-mes/elfarm-footer-single-main.hex2":()
<vagrantc>exiting...
<vagrantc>unhandled exception:error:(("mescc: file not found: \"linux/arm-mes/elfarm-footer-single-main.hex2\""))
<vagrantc>this was trying to build mes-mescc via ./configure --bootstrap
<OriansJ>vagrantc: mes.c doesn't use floating point instructions in the execution of mescc nor in the execution of mescc-tools and as the integer core instructions are the same between armv5 and armv7, mes should be able to run on armv5 just fine. However mescc choosing to fail is a different matter and probably why. (Not counting the missing hex2 elf headers)
<OriansJ>also it appears it is using the version of mescc-tools before we added powerpc64le support
<OriansJ>and did not include the fix to enable kfreebsd-amd64 to build properly.