all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: 42342@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#42342: Wine64 segfaults (5.12/staging)
Date: Fri, 31 Jul 2020 14:37:29 +0200	[thread overview]
Message-ID: <20200731123614.unf45a46y6etig2d@pelzflorian.localdomain> (raw)
In-Reply-To: <20200730145445.qmtnb6m77ogh4nfo@gravity>

On Thu, Jul 30, 2020 at 04:54:45PM +0200, Jakub Kądziołka wrote:
> $ guix environment --ad-hoc wine64 -- wine64 regedit
> 
> fired up the registry editor just fine.


Indeed, when running pure 64-bit applications (like VLC’s 64-bit
Windows build), using wine64 instead of wine works fine.  I did not
even know this command existed.

It seems the issue is only with WoW64, i.e. supporting both 32-bit and
64-bit programs.  The synopsis of wine64 claims it’s a WoW64 version.

For example, the installer of VLC’s 32-bit or 64-bit Windows version
fails to run.  The installer is claimed by binutils’ objdump program
to be a 32-bit i386 executable instead of i386:x86-64.

Regards,
Florian




  reply	other threads:[~2020-07-31 12:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  9:53 bug#42342: Wine64 segfaults (5.12/staging) Leo Prikler
2020-07-13 12:24 ` Leo Prikler
2020-07-28 16:53   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 17:36     ` Leo Prikler
2020-07-28 10:01 ` Pierre Neidhardt
2020-07-28 15:58   ` Pierre Neidhardt
2020-07-28 16:22     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 16:28       ` Pierre Neidhardt
2020-07-28 16:41         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-29 10:33           ` Pierre Neidhardt
2020-07-30 14:54     ` Jakub Kądziołka
2020-07-31 12:37       ` pelzflorian (Florian Pelz) [this message]
2020-08-09 13:38         ` Pierre Neidhardt
2020-08-09 14:03           ` Pierre Neidhardt
2020-08-09 15:03             ` Jakub Kądziołka
2021-05-11 15:40 ` Leo Prikler

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=20200731123614.unf45a46y6etig2d@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=42342@debbugs.gnu.org \
    --cc=kuba@kadziolka.net \
    --cc=mail@ambrevar.xyz \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.