Cannot compile with bitbridge anymore [Linux]

[DaforLynx]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

I dunno what I'm doing wrong, because I've been able to do it before, somehow. The build stops at the linking step. I use the standard ninja configuration with bitbridge listed in the readme.

/usr/bin/ld: cannot find -lole32: No such file or directory
/usr/bin/ld: skipping incompatible /usr/lib/libxcb.so when searching for -lxcb
/usr/bin/ld: cannot find -lshell32: No such file or directory
/usr/bin/ld: skipping incompatible /usr/lib/libuuid.so when searching for -luuid
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/g++ failed
ninja: build stopped: subcommand failed.

I looked up the libraries, and they appear to be Windows dlls? Not sure why I need them for the Linux build. Or where I would find them, or where I would put them. Some help would be appreciated.

Operating system

Arch

How did you install yabridge?

compile

yabridge version

commit dd36bb3

yabridgectl version

commit dd36bb3

Wine version

wine-10.9 (Staging)

Plugin

No response

Plugin type

None

Plugin architecture

None

Host

REAPER

Desktop environment or WM

No response

GPU model

No response

GPU drivers and kernel

No response

Debug log

No response

Anything else?

No response

[robbert-vdh]

See also #435.

Arch recently changed the way they build Wine to use the new WoW64 build mode (Arch news). Historically, Wine distributions contained a 64-bit version of Wine, as well as a 32-bit version that knew where to find the 64-bit version. This allowed you to run both 32-bit and 64-bit software in a single Wine prefix with some special magic, not unlike how it would work on Windows. That mechanism is called WoW64 (Windows 32-bit on Windows 64-bit). Recently-ish, Wine added a new WoW64 build mode that no longer relies on a 32-bit version of Wine and all of its dependencies being available, instead relying on a mechanism that's not unlike yabridge's own bitbridge to allow 64-bit Linux libraries to be used when running 32-bit Windows PE binaries. This greatly simplifies packaging for distro maintainers because you no longer need all of these 32-bit libraries at the cost of some performance overhead, but it does also mean that building 32-bit Winelib libraries, like yabridge's bitbridge, is just straight up not supported anymore (Wine issue #58377).

Supporting bitbridging with the new WoW64 Wine build would require a major rewrite of yabridge, as well as a way to use Wine's new WINE_UNIX_CALL interface to call into a native 64-bit library from a PE32 Windows binary. From the sound of it, that's not yet supported, and even if it were it would still require a lot of time and effort rearchitecturing yabridge.

So the TL;DR is that bitbridging isn't and likely won't be supported with Wine's new WoW64 mode. If you want to compile and/or use yabridge's bitbridge, you will need to use a Wine build that does not use the new WoW64 mode, like wine-tkg.

[DaforLynx]

Well, looks like wine-tkg works well. However, it doesn't appear to come with winegcc, or else something is preventing it from allowing me to compile yabridge builds, which prevents me from further testing. Luckily what I have installed works perfectly for me. Thanks for the quick response and help. I wish you the very best in dealing with these constant regressions. 😔