Github messages for voidlinux
 help / color / mirror / Atom feed
From: rilysh <rilysh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] wine 32bit: couldn't be able to find ntdll.so
Date: Fri, 31 Mar 2023 13:09:32 +0200	[thread overview]
Message-ID: <20230331110932.Zw4io-yjRySTFl0RANwH_pv3WSUs4YWfM512GOj2h4Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43132@inbox.vuxu.org>

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

Closed issue by rilysh on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.21_1 x86_64 GenuineIntel uptodate rrmFFF

### Package(s) Affected

wine-32bit-8.4_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

32-bit version of wine should run just fine.

### Actual behaviour

Launching wine (32-bit) literally throws that ntdll.so couldn't be found on its path. Running wine (64-bit) with its usual name, wine64 which runs just fine.

#### Message
wine (32-bit)
```
wine: could not load ntdll.so: /usr/libexec/wine/../../lib32/wine/i386-unix/ntdll.so: cannot open shared object file: No such file or directory
```

### Steps to reproduce

1. Enable multilib repositories in Void. Usually with (`xbps-install -Sy void-repo-multilib`)
2. Install wine regardless of its package name, wine-32bit with (`xbps-install -Sy wine-32bit`)
3. Open a terminal and run wine (which will now address 32-bit version of wine)


  parent reply	other threads:[~2023-03-31 11:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  6:33 [ISSUE] " rilysh
2023-03-31 10:05 ` amak79
2023-03-31 11:09 ` rilysh [this message]
2023-03-31 11:09 ` rilysh
2023-03-31 11:24 ` amak79
2023-03-31 11:24 ` amak79
2023-05-17  5:17 ` amak79
2023-05-17 18:18 ` Hoshpak
2023-05-17 20:11 ` [ISSUE] [CLOSED] " Hoshpak

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=20230331110932.Zw4io-yjRySTFl0RANwH_pv3WSUs4YWfM512GOj2h4Y@z \
    --to=rilysh@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).