From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [rfc] native aarch64 builders
Date: Wed, 14 Dec 2022 18:30:23 +0100 [thread overview]
Message-ID: <20221214173023.f_k0haD7NV7Q2udXS8r-gTmID3aMRwfDMZqrsb36b2U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40980@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/40980#issuecomment-1351824159
Comment:
It is simple to modify xbps-src to use qemu, just an example:
```patch
--- a/common/xbps-src/shutils/chroot.sh
+++ b/common/xbps-src/shutils/chroot.sh
@@ -160,7 +160,7 @@ chroot_handler() {
if [ "$action" = "chroot" ]; then
$XBPS_COMMONDIR/chroot-style/${XBPS_CHROOT_CMD:=uunshare}.sh \
- $XBPS_MASTERDIR $XBPS_DISTDIR "$XBPS_HOSTDIR" "$XBPS_CHROOT_CMD_ARGS" /bin/xbps-shell
+ $XBPS_MASTERDIR $XBPS_DISTDIR "$XBPS_HOSTDIR" "$XBPS_CHROOT_CMD_ARGS" /usr/bin/qemu-aarch64-static /bin/bash /bin/xbps-shell
rv=$?
else
env -i -- PATH="/usr/bin:$PATH" SHELL=/bin/sh \
@@ -178,7 +178,7 @@ chroot_handler() {
${XBPS_ALT_REPOSITORY:+XBPS_ALT_REPOSITORY=$XBPS_ALT_REPOSITORY} \
$XBPS_COMMONDIR/chroot-style/${XBPS_CHROOT_CMD:=uunshare}.sh \
$XBPS_MASTERDIR $XBPS_DISTDIR "$XBPS_HOSTDIR" "$XBPS_CHROOT_CMD_ARGS" \
- /void-packages/xbps-src $XBPS_OPTIONS $action $pkg
+ /usr/bin/qemu-aarch64-static /bin/bash /void-packages/xbps-src $XBPS_OPTIONS $action $pkg
rv=$?
fi
```
```sh
echo XBPS_CHROOT_CMD=bwrap >> etc/conf
./xbps-src binary-bootstrap -m maarch aarch64-musl
cp /usr/bin/qemu-aarch64-static maarch/usr/bin/
./xbps-src -m maarch pkg libtool
./xbps-src -m maarch pkg ntl
```
This assumes bubblewrap, qemu-user-static and binfmt are available on the host. It would have to be improved if it was meant to be merged to void-packages and it's very slow.
next prev parent reply other threads:[~2022-12-14 17:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 16:19 [ISSUE] " dkwo
2022-12-12 20:14 ` Eloitor
2022-12-12 20:28 ` classabbyamp
2022-12-12 20:53 ` dkwo
2022-12-12 21:54 ` Eloitor
2022-12-14 14:05 ` leahneukirchen
2022-12-14 14:06 ` tornaria
2022-12-14 14:07 ` leahneukirchen
2022-12-14 14:45 ` dkwo
2022-12-14 14:46 ` dkwo
2022-12-14 16:11 ` leahneukirchen
2022-12-14 16:28 ` dkwo
2022-12-14 17:30 ` paper42 [this message]
2022-12-15 23:00 ` leahneukirchen
2022-12-15 23:28 ` vincele
2023-01-07 15:19 ` dkwo
2023-02-10 5:29 ` BikyAlex
2023-02-10 5:29 ` BikyAlex
2023-04-12 8:43 ` vincele
2023-06-13 20:47 ` dkwo
2023-06-13 20:49 ` Duncaen
2023-06-13 20:50 ` Duncaen
2023-06-13 21:01 ` [ISSUE] [CLOSED] " Duncaen
2023-06-13 21:01 ` Duncaen
2023-06-13 21:02 ` Duncaen
2023-07-12 16:36 ` dkwo
2024-02-16 15:20 ` dkwo
2024-02-16 15:31 ` BikyAlex
2024-02-16 15:40 ` dkwo
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=20221214173023.f_k0haD7NV7Q2udXS8r-gTmID3aMRwfDMZqrsb36b2U@z \
--to=paper42@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).