Host Arm32 toolchain should be armv6

[ThadHouse]

We should be building the host arm32 toolchain against raspi-bullseye, as that is what all our libraries are built against so they work all the way down on the Pi 1.

[RyanHir]

There is a bootstrapping issue here. This project can build a toolchain targeting a different host than the build machine, but it is unable to build a toolchain that will then be used to build another toolchain. I chose to use the toolchains provided by Ubuntu because it was in the repositories. It might be possible to tell GCC (x86_64 build machine building a ARM32 hosted toolchain) to emit ARMv6 instructions (something like -march=armv6) but I worry that the object code that is included may have ARMv7 instructions (crt1.o, crti.o, etc.).

I do not imagine building C++ code on a Raspberry Pi 1 or 0 is a pleasant experience. Are you certain that these toolchains need to be run on these devices? With how the toolchains are currently built, they should work on the Pi 2 and up.

[ThadHouse]

Well like I posted in the other issue, could you use the docker images that already have the cross compilers in them? That’d solve both this issue and the other one. It’d be fine to use a compiler that was previously built and set up I’d think.

[PeterJohnson]

Fixed by #44.