From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: aarch64* exec format error post base-chroot install
Date: Sat, 20 Mar 2021 07:04:01 +0100 [thread overview]
Message-ID: <20210320060401.EYXZzwALoHEEncZRK7sZJuxESj924rZevZYS0CJnHnc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29603@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/29603#issuecomment-803257432
Comment:
On 2021-03-19 22:41:49-0700, Wayne Van Son ***@***.***> wrote:
> I don't quite understand. When I use any other arch excluding aarch64*, I don't get this problem.
What's the other arches? x86_64-musl and i686, I guess.
They can run natively in x86_64 ;)
>
> I'm using contributing a package template that doesn't cross compile
> (uses `haskell-stack`). I feel there shouldn't be any fluffing
> around to get something like this to work, as I've followed the
> instructions in the `README.md` for native compilation on
> a different arch.
Just mark it's as nocross.
>
> `qemu-aarch64-static` is available in my `"$PATH"`.
> I copied to both masterdirs and the output is still the same.
cp /usr/bin/qemu-aarch64-static $MASTERDIR/usr/bin/qemu-aarch64-static
>
> > enable binfmts support outside of chroot
> > ... and reconfigure your $MASTERDIR
>
> How could I go about this? I'm unsure of what the commands required.
xbps-install bintfmt-support
update-binfmts
--
Danh
prev parent reply other threads:[~2021-03-20 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 2:04 [ISSUE] " waynevanson
2021-03-20 2:14 ` sgn
2021-03-20 2:14 ` [ISSUE] [CLOSED] " sgn
2021-03-20 5:41 ` waynevanson
2021-03-20 6:04 ` sgn [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=20210320060401.EYXZzwALoHEEncZRK7sZJuxESj924rZevZYS0CJnHnc@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).