-
-
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
Wine not detected on Gentoo #4108
Comments
@Metalhead33 Instead of symlinking, you can try passing Did the location of Wine on the file system change with those packaging changes? If so, where to? Maybe we can add that path to our |
@lukas-w Thank you! Both "cmake .. -DCMAKE_PREFIX_PATH=/usr/lib/wine-vanilla-2.20" and "cmake .. -DCMAKE_PREFIX_PATH=/usr/lib/wine-vanilla-2.0.3" worked fine (at least as far as executing cmake and making it recognize wine, didn't try compiling yet). |
Aaaaaand, error!
Maybe if I tried with "cmake .. -DCMAKE_PREFIX_PATH=/usr/lib32/wine-vanilla-2.20" intead of "cmake .. -DCMAKE_PREFIX_PATH=/usr/lib/wine-vanilla-2.20"? Edit: Nope, even with that command, the same error happens. |
@Metalhead33 That's a known bug with winegcc. It automatically links to 64bit libraries even when building 32bit binaries using the What's the output of |
I have found a temporary workaround: /tmp/lmms/plugins/vst_base/CMakeLists.txt:
/tmp/lmms/cmake/modules/FindWine.cmake:
|
@lukas-w
|
Reopening because this is likely something we can improve upon. |
So tried this, seemed to work (thank you Metalhead33), but now getting
Not certain where X11EmbedContainer.h comes from, any idea? (Using Gentoo as well, relatively up to date system, and using Wine 2.0.3 |
@PhysSong explains this in #4124. Assuming you're on
@Metalhead33 can you see if this patch helps? |
@Metalhead33 final bump on this. It's already merged, but we'd love to know this platform is supported. I gave up trying to setup a Gentoo build environment so we'll have to defer this to someone more comfortable with the platform. |
FYI, I found that Gentoo supports two different multilib layouts. That may not be an issue because Wine 3.21 fixes the linking issue: wine-mirror/wine@2dfff7e |
I am a user of Gentoo Linux, and "somewhat recently" (in November, 2017), the other Gentoo people decided to completely repackage wine. Gone were the days of having to emerge "app-emulation/wine", instead it's now a combination of "virtual/wine" and "app-emulation/wine-vanilla", "app-emulation/wine-staging" or "app-emulation/wine-d3d".
What does that mean?
That means that everything wine-related is found somewhere else than before, unless I manually symlink or something.
Which in turn means this:
I want VST support, which is precisely why I am willing to clone the git source and compile from there instead of emerging "media-sound/lmms" (which doesn't have VST support). Will this be remedied eventually? Or do I have to manually symlink?
By the way, I have "=app-emulation/wine-vanilla-2.0.3" and "=app-emulation/wine-vanilla-2.20"
The text was updated successfully, but these errors were encountered: