From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Cross Compile Exec Error
Date: Sat, 14 Sep 2019 19:55:13 +0200 [thread overview]
Message-ID: <20190914175513.Esx78thFWnkbzfLBE3Zbszt4OKMuFIdnNmuDke0gzUU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14456@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
New comment by Piraty on void-packages repository
https://github.com/void-linux/void-packages/issues/14456#issuecomment-531500330
Comment:
how is that supposed to work?
`./xbps-src <binary->bootstrap <arch>` sets up a masterdir/chroot for the given arch (or the one you run on, if none is given).
you can't run arm code on an x86 (at least not in this chroot with xbps-src. qemu would be an option but that's not supported currently).
What you're probably after is `./xbps-src -a <arch>` if you intend to crosscompile from x86 to arm
next prev parent reply other threads:[~2019-09-14 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 17:46 [ISSUE] " voidlinux-github
2019-09-14 17:55 ` voidlinux-github [this message]
2019-09-14 17:55 ` [ISSUE] [CLOSED] " voidlinux-github
2019-09-14 17:59 ` voidlinux-github
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=20190914175513.Esx78thFWnkbzfLBE3Zbszt4OKMuFIdnNmuDke0gzUU@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).