Github messages for voidlinux
 help / color / mirror / Atom feed
From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [WIP] i686 chroot
Date: Tue, 11 Jan 2022 09:27:24 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34988@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

New issue by Anachron on void-packages repository

https://github.com/void-linux/void-packages/issues/34988

Description:
I'm currently testing a `i686` repo on `r32` with the following.

`wine` needs an ugly wrapper so far:

```
#!/bin/sh

export WINEDLLPATH="/lib/wine/i386-unix"
sudo -E chroot /r32 "/usr/libexec/wine/wine" "${@}"
```

`/usr/libexec/wine/wine` needs to be symlinked to this script in order for `/bin/wine` (see https://github.com/void-linux/void-packages/blob/master/srcpkgs/wine/files/wine) to find it. 
I've put `/usr/bin/chroot /r32` inside my `sudoers` file to not need to type any password for chroots on this path.

The tool `bottles` can now find and launch wine on `32bit`:

```
$ bottles
2022-01-11 09:13:38 INFO: Dxvk found: [dxvk-1.9.2]
2022-01-11 09:13:38 INFO: Vkd3d found: [vkd3d-proton-2.5]
2022-01-11 09:13:38 INFO: Nvapi found: [dxvk-nvapi-v0.5.1]
2022-01-11 09:13:38 INFO: Runners found: [sys-wine-7.0-rc5
|caffe-6.23]
2022-01-11 09:13:41 INFO: Bottles gestartet!
```

This is a WIP. 

             reply	other threads:[~2022-01-11  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  8:27 Anachron [this message]
2022-01-11 18:00 ` Duncaen
2022-01-12  5:53 ` Anachron
2022-04-13  2:08 ` github-actions
2022-04-13  5:32 ` Anachron
2022-04-13  5:32 ` [ISSUE] [CLOSED] " Anachron

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34988@inbox.vuxu.org \
    --to=anachron@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).