wine 10.0 linker error

  • Open
  • quality assurance status badge
Details
2 participants
  • glab
  • Liliana Marie Prikler
Owner
unassigned
Submitted by
glab
Severity
normal

Debbugs page

glab wrote 4 days ago
(address . bug-guix@gnu.org)
fd276d498e74cc1ddd8fb0ed05599491@disroot.org
Running 32-bit wine results in the following error:

bash: /gnu/store/sxbn4yi12jna12c4s8ab8wrb1n51hfhy-wine-10.0/bin/wine:
No such file or directory

That file actually does exist. Calling file on it provides this output:
/gnu/store/sxbn4yi12jna12c4s8ab8wrb1n51hfhy-wine-10.0/bin/wine: ELF
32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically
linked, interpreter
/gnu/store/hw6g2kjayxnqi8rwpnmpraalxi0djkxc-glibc-2.39/lib/ld-linux.so.2,
for GNU/Linux 3.2.0, stripped

However, the linked interpreter does not exist.

Rutherther kindly provided the following insight on IRC:
"wine(32) seems to work like this: "guix shell --system=i686-linux
wine", which is counterintuitive imo, x86_64 should either be
unsupported platform, or it should be made sure that it points to them
on x86_64 as well"

--
Gustavo
Liliana Marie Prikler wrote 3 days ago
976e47dd93a24a562cfbf9645416d8d51b6b85e2.camel@gmail.com
Am Samstag, dem 08.03.2025 um 00:06 +0000 schrieb glab:
Toggle quote (3 lines)
> Rutherther kindly provided the following insight on IRC:
> "wine(32) seems to work like this: "guix shell --system=i686-linux
> wine", which is counterintuitive imo
I can not confirm that it "works like this". I can confirm however,
that wine64 works as one would expect.

Toggle quote (2 lines)
> x86_64 should either be unsupported platform, or it should be made
> sure that it points to them on x86_64 as well"
wine32 is a dependency of wine64, so we do still need to build it
there. It seems that this i686 glibc actually has an x86_64 linker,
though. So something wrong is happening here.

Cheers
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 76849@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 76849
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help