On Wednesday, April 18, 2018 at 8:15:16 PM UTC+2, Henning Schild wrote:Am Wed, 18 Apr 2018 07:49:01 -0700
schrieb <j...@solid-run.com>:
> I figure someone with more experience would be able to determine that
> way this should work and hence a solution to a failure faster than me
> digging through the process.
>
> I am attempting to build a debian-jessie armhf image with my own
> custom kernel and the setup is failing in buildchroot.bb
>
> The final step is to run chroot configscript.sh, however the chroot
> is built with armhf binaries so dash fails to execute. Is this just
> an unsupported configuration?
At the point where you chroot into a buildchroot using a different
architecture, binfmt magic should kick in and will automagically run
everything in qemu-user-static. Make sure you have "qemu-user-static"
and "binfmt-support" installed. And make sure to execute
"/etc/init.d/binfmt-support start" to configure and enable the magic.
Henning
> Let me know any other information you would need.
>
> Thanks.
>
Thanks that helped a lot. I am building on CentOS 7 so the for reference the packages required are wine-systemd, and qemu-user