From: jon@solid-run.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Build failure when cross building for armhf on amd64
Date: Thu, 19 Apr 2018 00:29:45 -0700 (PDT) [thread overview]
Message-ID: <f1701536-593d-4455-87ec-0e2d9cdc9bbc@googlegroups.com> (raw)
In-Reply-To: <20180418201514.3d6ab66b@mmd1pvb1c.ad001.siemens.net>
[-- Attachment #1.1: Type: text/plain, Size: 1247 bytes --]
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 <javascript:>>:
>
> > 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
[-- Attachment #1.2: Type: text/html, Size: 2187 bytes --]
prev parent reply other threads:[~2018-04-19 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 14:49 jon
2018-04-18 18:15 ` Henning Schild
2018-04-19 7:29 ` jon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1701536-593d-4455-87ec-0e2d9cdc9bbc@googlegroups.com \
--to=jon@solid-run.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox