[Bug 49555] Wine-Staging compilation fails after 046f6604b763ca494bece1ff16a0919077ecb9d4 (../ntdll/unix/file.c)

[WineHQ Bugzilla]

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

--- Comment #6 from Béla Gyebrószki <gyebro69 at gmail.com> ---
(In reply to Olivier F. R. Dierick from comment #5)
> (In reply to Béla Gyebrószki from comment #2)
> > However, a WOW64 build is broken, simply issuing 'winecfg' to create/update
> > a WOW64 wineprefix results in multiple unhandled page faults and other nasty
> > issues. 32bit-only builds seem to work (at least the prefix creation part).
> > 
> > Sorry, no new bug report this time because I have other things to do for the
> > rest of the day, I hope you can sort it out.
> 
> Hello,
> 
> I have a similar issue running 'wineboot -u' to update wineprefixes from
> 5.10 to 5.11 or 5.12 (both vanilla wine and staging).
> 
> The commit 6f9d20806e821ab07c8adf81ae6630fae94b00ef was identified as the
> cause. Reverting it (and dependent commit
> 145cfce1135a7e59cc4c89cd05b572403f188161), fixes the update issue in both
> 5.11 and 5.12 for me.
> 
> I hope that this information will help you avoid a full regression test.
> 
> Regards.

Hello Olivier,

thanks for the heads up, I'll note that commit. I'm also seeing strange errors
in the terminal when updating an existing prefix, but didn't take time to track
it down. They appeared recently, in 5.11 I think.
>>00a8:err:x11settings:X11DRV_Settings_AddOneMode Maximum modes (116) exceeded
appears multiple times in the terminal when running 'wineboot -u', but it
doesn't seem to affect anything negatively.

However, this bug report was against a recent regression which occurred only in
Staging and it's already fixed in current staging/master.

Regards,
Béla

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