From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `./xbps-src bootstrap' fails
Date: Fri, 12 Feb 2021 18:21:17 +0100 [thread overview]
Message-ID: <20210212172117.sGr8BXqBwLJTewtv2y9jYXHP1qrvg0COMZAPGdUkKfA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25604@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/25604#issuecomment-778327962
Comment:
Yes `-a` instructs xbps to do cross compilation, without it its quite surprising that this does not fail earlier, but that is the issue.
Using `./xbps-src bootstrap cross-arch` is like creating a masterdir with `./xbps-src binary-bootstrap cross-arch` which is useless,
you want a build chroot that works on your host architecture and then cross compile from there with a cross toolchain.
next prev parent reply other threads:[~2021-02-12 17:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 18:27 [ISSUE] " ev-ermakov
2020-10-15 0:14 ` ahesford
2020-10-15 0:25 ` sgn
2020-10-15 0:26 ` sgn
2020-10-15 1:50 ` ev-ermakov
2020-10-15 14:06 ` sgn
2020-10-15 23:00 ` travankor
2020-10-16 0:20 ` sgn
2020-10-16 13:26 ` ev-ermakov
2020-10-16 13:44 ` ev-ermakov
2020-11-01 11:09 ` sgn
2020-12-11 1:17 ` [ISSUE] [CLOSED] " sgn
2021-02-12 16:32 ` RossComputerGuy
2021-02-12 16:40 ` RossComputerGuy
2021-02-12 17:21 ` Duncaen [this message]
2021-02-12 17:24 ` RossComputerGuy
2021-02-12 17:45 ` Duncaen
2021-02-12 17:47 ` RossComputerGuy
2021-02-12 17:57 ` RossComputerGuy
2021-02-12 17:57 ` RossComputerGuy
2021-02-12 18:03 ` Duncaen
2021-02-12 18:05 ` RossComputerGuy
2021-02-12 20:37 ` RossComputerGuy
2021-02-12 21:10 ` RossComputerGuy
2021-02-12 21:25 ` Duncaen
2021-02-12 21:28 ` RossComputerGuy
2021-02-12 21:29 ` Duncaen
2021-02-12 21:58 ` RossComputerGuy
2021-02-12 22:01 ` Duncaen
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=20210212172117.sGr8BXqBwLJTewtv2y9jYXHP1qrvg0COMZAPGdUkKfA@z \
--to=duncaen@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).