From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 42342@debbugs.gnu.org
Subject: bug#42342: Wine64 segfaults (5.12/staging)
Date: Sun, 9 Aug 2020 17:03:50 +0200 [thread overview]
Message-ID: <20200809150350.z5mvy3wv75oynjbb@gravity> (raw)
In-Reply-To: <87k0y7kjc4.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sun, Aug 09, 2020 at 04:03:07PM +0200, Pierre Neidhardt wrote:
> OK, I think I got it. I had to have _both_ wine and wine64 (staging or
> not) in my profile.
Interesting. Perhaps we should merge the two packages, then? We'd need
to take care to make it work right on i686-linux, but I don't think
that's unsurmountable...
> Previously, the "wine" executable (for 32-bit apps) used to work when
> wine64 alone was in the profile. Now it looks like we need both. Any
> idea what changed?
Perhaps loading 32-bit programs with the wine64 wasn't supposed to work
in the first place, and we were relying on some implementation quirk?
Alternatively, cross-compiling from 64 to 32 bit is less tested by
upstream than compiling natively on 64 or 32 bit, and we're hitting an
upstream bug?
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-09 15:05 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)
2020-08-09 13:38 ` Pierre Neidhardt
2020-08-09 14:03 ` Pierre Neidhardt
2020-08-09 15:03 ` Jakub Kądziołka [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200809150350.z5mvy3wv75oynjbb@gravity \
--to=kuba@kadziolka.net \
--cc=42342@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).