From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
Alexander Smirnov <asmirnov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Host with i686 kernel
Date: Wed, 2 May 2018 11:01:31 +0200 [thread overview]
Message-ID: <fa927b2f-cd67-28ca-9cb8-b43e982a3eb0@siemens.com> (raw)
In-Reply-To: <20180502105257.34308124@md1pvb1c.ad001.siemens.net>
On 2018-05-02 10:52, [ext] Henning Schild wrote:
> Am Tue, 1 May 2018 21:19:19 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>
>> Hi all,
>>
>> I've faced with the problem building Isar on i686 host kernel. The
>> amd64 configuration fails on debootstrap with error:
>>
>> - mount: cannot execute binary file: Exec format error
>>
>> As I found, this error happened when debootstrap tries to run
>> '/bin/mount' in chroot. The issue is that there is no binfmt for
>> x86_64.
>>
>> I've found a binfmt config for AMD64:
>>
>> http://seeblog.seenet.ca/2016/03/running-amd64-binaries-on-an-i386-linux-system/
>>
>> But it works very unstable (possibly this is the reason why it's not
>> included in default package).
>>
>> Conclusion: Isar can't build 64-bit systems on 32-bit host kernels.
>
> I think that is OK, 32bit x86 is dead. To follow up one could open a
> debian bug about the missing/broken binfmt and document that limitation
> in Isar.
It could easily be a qemu-user issue as well. QEMU always had problems
mapping the full register set of x86-64 on the constrained one of i386.
Plus, no one is using 32-bit anymore (except some crazy embedded and/or
nostalgic folks).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-05-02 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 18:19 Alexander Smirnov
2018-05-02 8:52 ` Henning Schild
2018-05-02 9:01 ` Jan Kiszka [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=fa927b2f-cd67-28ca-9cb8-b43e982a3eb0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=henning.schild@siemens.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