-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RemoteVstPlugin fails to build with with -flto #5179
Comments
It seems like it's a bug with Wine >= 4.14: https://bugs.winehq.org/show_bug.cgi?id=47710 |
With -D__WIDL_objidl_generated_name_0000000C="" included in the CXXFLAGS I get a link time error about an undefined ExitProcess due to the vst section choking on Link Time Optimization. This is a pity because everything else except vst builds with it. I've discovered that I can build the vst plugins without wine which is the best option for me, works with LTO as well. |
That sounds like https://bugs.winehq.org/show_bug.cgi?id=41712 |
Can confirm it is. |
I think we can close this issue? @PhysSong |
The |
try commenting out
I had to do this to compile Carla |
I've revisited openSUSE's lmms build and the only build flag I have to remove is -m64 to allow the wine-32 build to succeed. grepping the build log finds 167 instances of -flto=auto so I don't understand the issue with lto. The only modification to the build is sed out -m64 and add -D__WIDL_objidl_generated_name_0000000C="" to the build flags. |
The problem is still there on Fedora 34/i686, I think (for lmms 1.2.2):
with these wine packages installed:
Compilation succeeds when omitting NB: Adding |
Is this issue impacted at all by #6672 (comment) ? |
I'm closing this for now as we switched to use wine >= 6.0 and i persume the regression to not be there. If it arises again, feel free to reopen. |
I've disabled vst build in openSUSE meanwhile but maybe it's easy for someone familiar with lmms to find a fix. I've attached the entire build log. See:
https://build.opensuse.org/package/show/multimedia:apps/lmms to view the patches.
Build failure point:
rpmbuildlog.txt
The text was updated successfully, but these errors were encountered: