it would seem that someone, somewhere is seting up binfmt_misc + qemu-arm-static to be located /usr/bin. I say this given the following:
root@neptune:/bld/developer-cross# chroot ./chroot /bin/bash --login
chroot: failed to run command `/bin/bash': No such file or directory
root@neptune:/bld/developer-cross# ls chroot/bin/
bash ln sleep
...
And thus it works. I'd been putting qemu-static* into /exp so I could easily delete it from the chroot on cleanup of the rootfs as it was being built.
I haven't seen a way to query where qemu has to be installed in order for apps of that arch to work via binfmt. I'm happy to change live-build3 so that it uses this same hardcoded position, just be nice to have a way to programmatically do the right thing.
it would seem that someone, somewhere is seting up binfmt_misc + qemu-arm-static to be located /usr/bin. I say this given the following:
root@neptune: /bld/developer- cross# chroot ./chroot /bin/bash --login /bld/developer- cross# ls chroot/bin/
chroot: failed to run command `/bin/bash': No such file or directory
root@neptune:
bash ln sleep
...
root@neptune: /bld/developer- cross# cp chroot/exp/qemu-arm /bld/developer- cross# cp chroot/ exp/qemu- arm* chroot/usr/bin/. /bld/developer- cross# chroot ./chroot /bin/bash --login
qemu-armeb-static qemu-arm-static
root@neptune:
root@neptune:
root@neptune:/#
And thus it works. I'd been putting qemu-static* into /exp so I could easily delete it from the chroot on cleanup of the rootfs as it was being built.
I haven't seen a way to query where qemu has to be installed in order for apps of that arch to work via binfmt. I'm happy to change live-build3 so that it uses this same hardcoded position, just be nice to have a way to programmatically do the right thing.