[Bug 44851] New: Unable to create 32-bit wineprefix in FreeBSD
https://bugs.winehq.org/show_bug.cgi?id=44851 Bug ID: 44851 Summary: Unable to create 32-bit wineprefix in FreeBSD Product: Wine Version: 3.4 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lehmannwer(a)gmail.com Using FreeBSD amd64 11.1-RELEASE-p4, nvidia-driver-390.25, wine-devel 3.4 from packages. After installing the wine package and running "wine winecfg", it successfully created a new .wine directory asking and downloading gecko. But when additionally trying to create a 32-bit environment as described in section 6.5.3 of the FAQ, I get the following error: $ WINEARCH=win32 WINEPREFIX=/home/werner/wine32bit winecfg wine: created the configuration directory '/home/werner/wine32bit' wine: '/home/werner/wine32bit' is a 32-bit installation, it cannot support 64-bit applications. The folder wine32bit is actually created, but it looks like winecfg is not really executed, as the directory is not populated with anything but and empty folder "drive_c" and "dosdevices" with two links to "c" and "z". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- According to the wiki (https://wiki.winehq.org/FreeBSD)
FreeBSD can actually build and run the pure 64-bit version of wine now. The problem is that it still doesn't support WoW64, and since that's necessary for the overwhelming majority of Windows apps, amd64 systems still need to use the 32-bit package.
So it seems that you have 64bit wine installed, but that doesn't have 32bit support. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 --- Comment #2 from lehmannwer(a)gmail.com --- OK, I understand now. So what is the status on that matter? When will FreeBSD support WoW64 then? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- (In reply to lehmannwer from comment #2)
OK, I understand now. So what is the status on that matter? When will FreeBSD support WoW64 then?
That's a question for FreeBSD packagers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- FreeBSD issue, not Wine's, marking NOTOURBUG. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44851 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the spam. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org