please dont send a tarball, send a patch, or even better fork it on github and put your patches there (you can open a pull request, and pikhq will most likely accept it)jamesbond wrote: If the mailing list accepts attachment I'll probably package the modified bootstrap tarball hardcoded to build for arm-eabi (the generic "export A=arm" won't work directly).
the problem is that sabotage consists of 100+ packages, and most of them can't be cross compiled without huge patch orgies. otoh bootstrap linux consists only of a kernel, busybox and a toolchain, all of them designed for cross compilation.jamesbond wrote: Sabotage native build worked fine (I tested in x86_64 arch), but just that it won't cross compile (well not easily) and Ibidem told me you have no plans to make it so.
the rootfs that's linked there is a generic ARMv7l softfp (vfp) rootfs (no kernel included). it should be possible to use it with qemu (you'll need to specify a kernel on the qemu command line, for example the one aboriginal uses, or one you built yourself with the config aboriginal uses)jamesbond wrote:That's for efikamx though, I don't have the hardware.want an existing sabotage ARMV7l rootfs ? look at
https://github.com/rofl0r/sabotage/wiki/efika_mx
yep crux should work as well, and it should be possible to bootstrap sabotage on it.jamesbond wrote: Your wiki page there links to crux-arm, and crux-arm rootfs supports qemu versatible-pb too. Will that work? I should give it a try.
btw, if you or somebody else plays around with musl and have any issues, join #musl irc channel instead of wasting your time fixing issues that were fixed dozens of times before.
there is a number of well known issues which will lead to segfaults (for example distro toolchains that remove the sysv hash section from binaries will crash on the musl dynlinker). all of them will be detected by a musl veteran in no time.
that said, i hope to see you on IRC, so we can help getting something started quickly.
i really don't like hanging around in forums...
good luck.