Add option to winebuild to disable ASLR/dynamicbase
Tres Finocchiaro <[email protected]> Mon, 7 Jul 2025 11:41:02 -0400
| Newsgroups | gmane.comp.emulators.wine.devel |
|---|---|
| Message-ID | <CANQs7dDp65g9zp=X+QTWny8jKFtY+cbHuOj1pHqc2zLgnOhzVQ@mail.gmail.com> |
Hi, I'm a maintainer of LMMS and we use a wine bridge for loading 32-bit and 64-bit VST plugins into the Linux version of our software. We've recently updated our build tools and noticed that some of our older 64-bit VSTs fail to load. After a lot of back and forth, we've isolated the issue to the following wine commit: > Commit 518e394 julliard committed on Sep 25, 2023 > winebuild: Set ASLR-related dll flags by default. > https://github.com/wine-mirror/wine/commit/518e394794160818ffe6826c874ff2f550c95bbb One of our developers has proposed a patch which reverts this behavior here: https://github.com/Fastigium/winebuild/commit/7f9e27e44cfb8eba79f3850f46e12fbe3f4875a5 My questions are as follows: 1. Would winehq be receptive to a winebuild flag that allows the old behavior? 2. If acceptable, would you prefer LMMS author this patch, or is this change trivial enough/small enough that the winehq team would prefer to tackle it themselves? 3. Lastly, quoting a past mailing list convo, should we be doing our wine bridge differently? Currently we build RemovePluginVst64.so.exe. "[...] I don't think we have any plans to deliberately break the old all-in-one .dll.so binaries. It is quite likely that this functionality will bitrot over time though. Also the functionality that the PE/unix split was introduced for won't be available that way [...]" Source: https://list.winehq.org/mailman3/hyperkitty/list/[email protected]/message/5PBWZ4ACVLLL4B43WFHBJYMZ7WB5POGF/ Thanks kindly for your time, -Tres - [email protected]