[Bug 41378] wineboot silently ignores unknown WINEARCH

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=41378

--- Comment #6 from Austin English <austinenglish at gmail.com> ---
(In reply to fjfrackiewicz from comment #5)
> (In reply to Jens Reyer from comment #4)
> > (In reply to fjfrackiewicz from comment #3)
> > > This patch won't interfere with the creation of WoW64 prefixes, will it?
> > 
> > AFAIK WoW64 has arch win64, there's nothing like e.g. WINEARCH=wow64. So I'd
> > say no, it won't interfere.
> > 
> > Thanks Austin!
> 
> Aha, so if I create a prefix with the following command:
> 
> WINEPREFIX=$HOME/.wine winecfg wineboot (I assume this is what creates a
> WoW64 prefix where I can run 32-bit applications alongside 64-bit ones)

A WoW64 (win64) prefix will be made if you have wine64, otherwise it would be
win32. Also note that that command runs winecfg (which would invoke wineboot if
the prefix wasn't updated or didn't exist).

> I will simply get an "unknown arch" error? 

No. You're not specifying a WINEARCH, so the default will be used (depending on
your wine setup).

You'd want:
WINEARCH=win32 wine wineboot

or:
WINEARCH=win64 wine wineboot

See
https://wiki.winehq.org/FAQ#How_do_I_create_a_32_bit_wineprefix_on_a_64_bit_system.3F
for more info.


You'll only get an error if the WINEARCH is invalid, e.g.,:
WINEARCH=foobar wine wineboot

which currently is allowed.

-- 
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.