From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6545800489054765056 X-Gmail-Labels: Topic type: DISCUSSION Date: Thu, 19 Apr 2018 00:29:45 -0700 (PDT) From: jon@solid-run.com To: isar-users Message-Id: In-Reply-To: <20180418201514.3d6ab66b@mmd1pvb1c.ad001.siemens.net> References: <8c0abfaa-66a5-4778-8bc2-bab09490c663@googlegroups.com> <20180418201514.3d6ab66b@mmd1pvb1c.ad001.siemens.net> Subject: Re: Build failure when cross building for armhf on amd64 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1348_584300076.1524122986085" X-Google-Token: EOmK4dYFVpYlRh8ohqw0 X-Google-IP: 195.192.248.120 X-TUID: n47KmxCVuwOk ------=_Part_1348_584300076.1524122986085 Content-Type: multipart/alternative; boundary="----=_Part_1349_1395150296.1524122986085" ------=_Part_1349_1395150296.1524122986085 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 >: > > > 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 ------=_Part_1349_1395150296.1524122986085 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Wednesday, April 18, 2018 at 8:15:16 PM UTC+2, Henning = Schild wrote:
Am Wed, 18 Apr 20= 18 07:49:01 -0700
schrieb <j...@solid-run.com>:

> I figure someone with more experience would be able to determine t= hat
> way this should work and hence a solution to a failure faster than= me
> digging through the process.
>=20
> I am attempting to build a debian-jessie armhf image with my own
> custom kernel and the setup is failing in buildchroot.bb
>=20
> The final step is to run chroot configscript.sh, however the chroo= t
> is built with armhf binaries so dash fails to execute. =C2=A0Is th= is 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-stat= ic"
and "binfmt-support" installed. And make sure to execute
"/etc/init.d/binfmt-support start" to configure and enable th= e magic.

Henning

> Let me know any other information you would need.
>=20
> Thanks.
>=20


Thanks that helped a lot.=C2=A0 I am b= uilding on CentOS 7 so the for reference the packages required are=C2=A0win= e-systemd, and qemu-user
=C2=A0
------=_Part_1349_1395150296.1524122986085-- ------=_Part_1348_584300076.1524122986085--