From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6545800489054765056 Date: Wed, 18 Apr 2018 07:49:01 -0700 (PDT) From: jon@solid-run.com To: isar-users Message-Id: <8c0abfaa-66a5-4778-8bc2-bab09490c663@googlegroups.com> Subject: Build failure when cross building for armhf on amd64 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_32145_2119589126.1524062941079" X-Google-Token: EN213dYFNBwkwZPSUss0 X-Google-IP: 195.192.248.120 X-TUID: y0O0H2o1lPJM ------=_Part_32145_2119589126.1524062941079 Content-Type: multipart/alternative; boundary="----=_Part_32146_1100536395.1524062941079" ------=_Part_32146_1100536395.1524062941079 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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? Let me know any other information you would need. Thanks. ------=_Part_32146_1100536395.1524062941079 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I figure someone with more experience would be able to det= ermine that way this should work and hence a solution to a failure faster t= han me digging through the process.

I am attempting to b= uild a debian-jessie armhf image with my own custom kernel and the setup is= failing in buildchroot.bb

The final step is to ru= n chroot configscript.sh, however the chroot is built with armhf binaries s= o dash fails to execute.=C2=A0 Is this just an unsupported configuration?

Let me know any other information you would need.

Thanks.
------=_Part_32146_1100536395.1524062941079-- ------=_Part_32145_2119589126.1524062941079--