It seems like it's necessary to have some files in /usr/lib (for 64 bit) and /usr/lib32 (for 32 bit) to be able to compile packages that depend on/need to link with wine: I've validated that adding the following symlinks using wineasio (https://sourceforge.net/projects/wineasio/) makes compilation work: 64bit: /usr/lib64/libwine.so -> /usr/lib64/wine-staging-2.19/libwine.so /usr/lib64/libwine.so.1 -> /usr/lib64/wine-staging-2.19/libwine.so.1 /usr/lib64/libwine.so.1.0 -> /usr/lib64/wine-staging-2.19/libwine.so.1.0 /usr/lib64/wine -> /usr/lib64/wine-staging-2.19/wine 32bit: /usr/lib32/libwine.so -> /usr/lib32/wine-staging-2.19/libwine.so /usr/lib32/libwine.so.1 -> /usr/lib32/wine-staging-2.19/libwine.so.1 /usr/lib32/libwine.so.1.0 -> /usr/lib32/wine-staging-2.19/libwine.so.1.0 /usr/lib32/wine -> /usr/lib32/wine-staging-2.19/wine So basically create a symlink for everything under /usr/lib[32|64|/<selected-wine-version> in /usr/lib[32|64]
I can confirm this for "airwave" (not in official portage, https://github.com/phantom-code/airwave). I can only build this software by setting the mentioned links manually. This is probably a problem for many other software as well.
There are also files in wine-vanilla, e.g. /usr/lib*/wine-vanilla-2.0.3/wine/acledit.dll.so, that point to a missing libwine.so.1: $ ldd /usr/lib64/wine-vanilla-2.0.3/wine/acledit.dll.so linux-vdso.so.1 (0x00007ffcf8926000) libwine.so.1 => not found libc.so.6 => /lib64/libc.so.6 (0x00007fe811a34000) /lib64/ld-linux-x86-64.so.2 (0x00007fe811ff9000) $ ldd /usr/lib32/wine-vanilla-2.0.3/wine/acledit.dll.so linux-gate.so.1 (0xf7efb000) libwine.so.1 => not found libc.so.6 => /lib32/libc.so.6 (0xf7cb2000) /lib/ld-linux.so.2 (0xf7efc000)
(In reply to Fabio Rossi from comment #2) > There are also files in wine-vanilla, e.g. > /usr/lib*/wine-vanilla-2.0.3/wine/acledit.dll.so, that point to a missing > libwine.so.1: > > $ ldd /usr/lib64/wine-vanilla-2.0.3/wine/acledit.dll.so > linux-vdso.so.1 (0x00007ffcf8926000) > libwine.so.1 => not found > libc.so.6 => /lib64/libc.so.6 (0x00007fe811a34000) > /lib64/ld-linux-x86-64.so.2 (0x00007fe811ff9000) > > $ ldd /usr/lib32/wine-vanilla-2.0.3/wine/acledit.dll.so > linux-gate.so.1 (0xf7efb000) > libwine.so.1 => not found > libc.so.6 => /lib32/libc.so.6 (0xf7cb2000) > /lib/ld-linux.so.2 (0xf7efc000) I have the extra 8 symlinks implemented in my Overlay app-emulation/wine-vanilla::bobwya. I see: ldd /usr/lib64/wine-vanilla-2.0.3/wine/acledit.dll.so linux-vdso.so.1 (0x00007fff76d38000) libwine.so.1 => /usr/lib64/libwine.so.1 (0x00007f8559d6e000) libm.so.6 => /lib64/libm.so.6 (0x00007f8559a67000) libc.so.6 => /lib64/libc.so.6 (0x00007f85596b7000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f85594b3000) /lib64/ld-linux-x86-64.so.2 (0x00007f855a34d000) ldd /usr/lib32/wine-vanilla-2.0.3/wine/acledit.dll.so linux-gate.so.1 (0xf7f41000) libwine.so.1 => /usr/lib32/libwine.so.1 (0xf7cdd000) libm.so.6 => /lib32/libm.so.6 (0xf7c80000) libc.so.6 => /lib32/libc.so.6 (0xf7ab8000) libdl.so.2 => /lib32/libdl.so.2 (0xf7ab3000) /lib/ld-linux.so.2 (0xf7f42000) So no additional symlinks are required - beyond those suggested in the original Description by Simon.
For wineasio in the proaudio overlay, I chose another approach. It use equery to determine the libdir of the installed wine flavor. You can read it online at https://svnweb.tuxfamily.org/filedetails.php?repname=proaudio%2Fproaudio&path=%2Ftrunk%2Foverlays%2Fproaudio%2Fapp-emulation%2Fwineasio%2Fwineasio-9999.ebuild
