From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC/tracking issue] deprecating -lib32 multilib system
Date: Thu, 07 Jan 2021 21:31:37 +0100 [thread overview]
Message-ID: <20210107203137.1sI8-Z6mZaTzvFRwyiaa0pQJh7XnxXhKA3AshEeuGJU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27337@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/27337#issuecomment-756366215
Comment:
I just did this on an `aarch64` installation on a Raspberry Pi, when I realized I couldn't run `retroarch` because all of the cores precompiled by that project are 32-bit only. Enter multilib forr ARM. Except for the repository path differences (an easy fix), everything worked beautifully.
```bash
mkdir -p /usr/armv7l/etc/xbps.d
echo "repository=https://mirrors.servercentral.com/voidlinux/current" > /usr/armv7l/etc/xbps.d/00-repository-main.conf
XBPS_ARCH=armv7l xbps-install -S -C /usr/armv7l/etc/xbps.d retroarch mesa-dri
rm -rf /usr/lib32 && ln -s armv7l/usr/lib /usr/lib32
ln -s /usr/armv7l/usr/lib/ld-2.30.so /usr/lib/ld-linux-armhf.so.3
/usr/armv7l/usr/bin/retroarch
```
We could wrap this in a simple script that derives `XBPS_ARCH` from the executable name (*e.g.*, `xbps-install-<arch>`) which can check for `/some/path/to/<arch>`, complain if it finds no `etc/xbps.d/00-repository-main.conf` (or maybe prepopulate the file) and make the necessary links after installation if they are missing.
next prev parent reply other threads:[~2021-01-07 20:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 0:50 [ISSUE] tracking issue: " q66
2020-12-22 1:17 ` [RFC/tracking issue] " ahesford
2020-12-22 1:18 ` q66
2020-12-22 1:22 ` Skirmisher
2020-12-22 1:58 ` q66
2020-12-22 2:00 ` q66
2020-12-22 2:05 ` ericonr
2020-12-22 4:31 ` ericonr
2020-12-22 4:31 ` ericonr
2020-12-22 5:11 ` ericonr
2020-12-22 5:26 ` ericonr
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 21:22 ` q66
2020-12-22 21:34 ` q66
2020-12-22 21:58 ` q66
2020-12-22 22:16 ` q66
2020-12-23 0:26 ` q66
2020-12-23 0:26 ` q66
2020-12-23 0:27 ` q66
2020-12-23 0:39 ` q66
2020-12-27 20:07 ` ericonr
2020-12-27 20:26 ` ericonr
2020-12-28 1:35 ` ericonr
2021-01-07 20:31 ` ahesford [this message]
2022-05-01 2:14 ` github-actions
2022-05-01 5:45 ` the-maldridge
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=20210107203137.1sI8-Z6mZaTzvFRwyiaa0pQJh7XnxXhKA3AshEeuGJU@z \
--to=ahesford@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).