4 ms·
You're welcome to join! Installation requires the 32 bit Wine runtime, which will require pulling in your distro's 32 bit libs. After that set export WINEA
by HeckFeck 5y ago
You're welcome to join!
Installation requires the 32 bit Wine runtime, which will require pulling in your distro's 32 bit libs. After that set
export WINEARCH="win32"
in your env, just run setup and all is golden.
It is worth noting that Office 97 + all deps required for 32 bit Wine is still a smaller installation size than any recent Office.
- kbenson 5y agoInterestingly, this announcement makes it sound like you might not even need 32-bit libraries anymore: - The 64-bit Windows-on-Windows (WoW64) architecture is implemented, and supports running a 32-bit Windows application inside a 64-bit Unix host process, using thunks to map 32-bit NT system calls to the 64-bit NTDLL. - WoW64 thunks are implemented for most Unix libraries, enabling a 32-bit PE module to call a 64-bit Unix library. Once the remaining modules are converted to PE, this will make it possible to run 32-bit applications without installing 32-bit Unix libraries.
- vetinari 5y agoI wonder how that will work on M1 macs. Right now, trying to run any 32-bit executable with Wine 6 is being met with "bad CPU type in executable".
- my123 5y agoCrossOver’s Wine builds have wine32on64 to run x86_32 programs using Rosetta 2 on M1 macs. Available at https://github.com/Gcenx/homebrew-wine https://github.com/Gcenx/homebrew-wine if you want to use a free build for example.