https://bugs.winehq.org/show_bug.cgi?id=39024
Bug ID: 39024 Summary: WINEARCH no longer creates a 32-bit wineprefix properly Product: Wine Version: 1.7.47 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: susancragin@gmail.com Distribution: ---
The program seems to default to a .wine64 prefix, even using the standard WINEARCH=win32 command.
So WINEARCH=win32 wine-development winecfg
gets you a .wine64 prefix.
BUT if you add WINEPREFIX=~/.wine to the mix you get the 32-bit wineprefix but then winecfg can't find it from the command line.
https://bugs.winehq.org/show_bug.cgi?id=39024
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- This is most likely a side-effect of the wrapper scripts shipped with the Debian packages. Please try to run Wine directly, without the wrapper scripts inbetween. The real executable is located at:
/usr/lib/wine-development/wine
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #2 from Susan Cragin susancragin@gmail.com --- (In reply to Sebastian Lackner from comment #1)
:/usr/lib/wine-development$ ls wine64 wine64-preloader wineapploader
No wine, no wine folder.
:/usr/lib/wine-development$ wine64 winecfg bash: wine64: command not found
And wine64's not a folder, either.
??
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Susan Cragin from comment #2)
That looks like you forgot to install the 32-bit packages. To do that, please run (as root):
dpkg --add-architecture i386 apt-get update apt-get install wine32-development
You are executing it incorrect, you have to type a relative path for all programs which are not included in the PATH environment variable.
In this case (when you are already in the /usr/lib/wine-development directory), it is sufficient to type:
./wine winecfg
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Sebastian Lackner from comment #3)
./wine winecfg
I meant "./wine64 winecfg" of course.
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #5 from Susan Cragin susancragin@gmail.com ---
I meant "./wine64 winecfg" of course.
/usr/lib/wine-development$ ./wine64 winecfg wine: could not exec the wine loader
??
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #6 from Susan Cragin susancragin@gmail.com --- More info
:/usr/bin$ ls wine* wineboot-development winecfg-development winedbg-development wine-development winefile-development winegcc64-development winepath-development
https://bugs.winehq.org/show_bug.cgi?id=39024
--- Comment #7 from Susan Cragin susancragin@gmail.com --- You are right that I didn't have the 386 packages. They must have been wiped out in an apt-get dist-upgrade. So I tried reactivating the 386 repos according to your instructions, and checking that my sources.list included the 386 packages.
$ sudo apt-get install libwine-development:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: libwine-development:i386 : Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
So what used to work now does not, and I have no 386 packages.
So there's something funny in Debian-land. And this bug is probably invalid.
https://bugs.winehq.org/show_bug.cgi?id=39024
Susan Cragin susancragin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #8 from Susan Cragin susancragin@gmail.com --- If I had to guess, I'd say this has something to do with the conversion to a new version of GCC. Some packages have been done, some have not. An interesting side-note is that attempts to reinstall have insisted that I remove Calibre. Oh, well. Marking invalid and moving on.
https://bugs.winehq.org/show_bug.cgi?id=39024
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Distribution|--- |Debian Summary|WINEARCH no longer creates |WINEARCH no longer creates |a 32-bit wineprefix |a 32-bit wineprefix |properly |properly (broken/incomplete | |Wine installation after | |Debian dist-upgrade)
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello folks,
you should at least rephrase the summary otherwise you might cause confusion among people using Bugzilla search/bug creation form.
Generic summaries tend to turn up in Bugzilla search list quite easily, tricking novice users into subscribing them or even worse trigger support requests "me too".
Regard
https://bugs.winehq.org/show_bug.cgi?id=39024
Susan Cragin susancragin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|WINEARCH no longer creates |Debian repositories do not |a 32-bit wineprefix |have all 386 wine packages, |properly (broken/incomplete |causing breakage in |Wine installation after |libwine-development:386 (as |Debian dist-upgrade) |of 3-Aug-2015)
https://bugs.winehq.org/show_bug.cgi?id=39024
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com --- Closing invalid bugs.
-
wine-bugs＠winehq.org