Date: Sun, 24 May 2020 14:13:28 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Damjan Jovanovic <damjan.jov@gmail.com> Cc: freebsd-emulation@freebsd.org Subject: Re: Wine 5.9 bugfix Message-ID: <alpine.LSU.2.21.2005241411520.4832@anthias.pfeifer.com> In-Reply-To: <CAJm2B-mg8BdGKCXJEgYT79QwNVGrT1COfOpRwHDCDkub1eoseQ@mail.gmail.com> References: <CAJm2B-m1JU%2B6J88=7r19cP9y=UXV%2BYmMQwoJgA_Ce1-bWPjiKA@mail.gmail.com> <alpine.LSU.2.21.2005232130580.4832@anthias.pfeifer.com> <CAJm2B-mg8BdGKCXJEgYT79QwNVGrT1COfOpRwHDCDkub1eoseQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 May 2020, Damjan Jovanovic wrote: >> I just started test builds of emulators/wine-devel with that patch. >> >> So far I have kept files/patch-tools-winegcc which reverts the upstream >> change (1ccd638b1aa85fb3c43b49d69d279cd509ebdc21) that kicked of this >> avalanche of events. I was thinking to keep that as part of our port >> until the next snapshot (Wine 5.10) - do you have any strong feelings >> or recommendations either way? > While I don't completely understand the many changes there, I would > advise against files/patch-tools-winegcc as Linux doesn't use it, and > the only issue on FreeBSD was that rtld-elf problem which Wine worked > around in 5.9. Okay, then I'll take that one out while adding one for the straightforward bug fix. That commit should land in the next hours, and then we've got nearly two weeks to gain experience and feedback before Wine 5.10 is expected. Thanks, Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.21.2005241411520.4832>