Package Details: yabridge 3.1.0-1

Git Clone URL: (read-only, click to copy)
Package Base: yabridge
Description: A modern and transparent way to use Windows VST2 and VST3 plugins on Linux
Upstream URL:
Licenses: GPL3
Submitter: robbert-vdh
Maintainer: robbert-vdh
Last Packager: robbert-vdh
Votes: 6
Popularity: 0.80
First Submitted: 2020-05-03 14:35
Last Updated: 2021-04-15 13:37

Latest Comments

1 2 3 Next › Last »

robbert-vdh commented on 2021-04-15 13:31

@phunni Ah yes, good catch, I forgot to add a makedepends version bound for Wine. Wine 6.6 has a regression with its wineg++ implementation that resets the include paths, and thus breaks includes like this. You'll either have to temporarily downgrade to Wine (Staging) 6.0-6.5 or use the prebuilt binaries from the yabridge-bin package.

phunni commented on 2021-04-15 13:28

Latest build fails with:

[8/31] Compiling C++ object libvst3_base_wine_64bit.a.p/meson-generated_vst3_base_wine_64bit-unity0.cpp.o FAILED: libvst3_base_wine_64bit.a.p/meson-generated_vst3_base_wine_64bit-unity0.cpp.o wineg++ -Ilibvst3_base_wine_64bit.a.p -I. -I.. -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c++2a -O3 -march=x86-64 -mtune=generic -O2 -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -isystem../subprojects/vst3 -isystemsubprojects/vst3 -DRELEASE=1 -DNOMINMAX -DWINE_NOWINSOCK -m64 -Wno-cpp -MD -MQ libvst3_base_wine_64bit.a.p/meson-generated_vst3_base_wine_64bit-unity0.cpp.o -MF libvst3_base_wine_64bit.a.p/meson-generated_vst3_base_wine_64bit-unity0.cpp.o.d -o libvst3_base_wine_64bit.a.p/meson-generated_vst3_base_wine_64bit-unity0.cpp.o -c libvst3_base_wine_64bit.a.p/vst3_base_wine_64bit-unity0.cpp In file included from /home/paul/.cache/aurutils/sync/yabridge/src/yabridge-3.1.0/build/../subprojects/vst3/base/source/fbuffer.cpp:40, from libvst3_base_wine_64bit.a.p/vst3_base_wine_64bit-unity0.cpp:2: /usr/include/c++/10.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory 75 | #include_next <stdlib.h> | ^~~~~~~~~~ compilation terminated. winegcc: /usr/bin/g++ failed

capoeira commented on 2021-02-16 20:15

@robbert-vdh damn, that was a nasty "bug". working fine now; thanks a lot

robbert-vdh commented on 2021-02-16 18:57

@capoeira Apparently the pt_BR.UTF-8 breaks the format for no reason by translating Mem: with Mem.:. I've updated the PKGBUILD and the RAM detection should now work with Brazilian locales.

robbert-vdh commented on 2021-02-16 17:27

Huh yours has a dot after Mem, that's very odd. I can imagine that breaking a number of things. Could you check whether env LANG=C free --gibi --si doesn't have that dot? I'll add that to the PKGBUILD then if this is caused by a broken translation.

capoeira commented on 2021-02-16 17:24

it's in portuguese, yes (I use systemd-swap)

[studio@bahiahost ~]$ free --gibi --si total usada livre compart. buff/cache disponível Mem.: 8 2 2 0 2 5 Swap: 0 0 0

robbert-vdh commented on 2021-02-16 16:44

@capoeira And what does running just free --gibi --si print? Does the output of free gets translated somehow? (there are no Dutch translation for it, and I assumed all of these system utilities aren't translated to prevent scripts from breaking)

capoeira commented on 2021-02-16 16:42

it doesn't output anything at all

robbert-vdh commented on 2021-02-16 15:57

@capoeira What's the output of free --gibi --si | awk '/^Mem:/ { print $2 }' on your system? If that's between 4 and 8 (inclusive) then the build should use three jobs, which on my system only 2.4 gigabytes of RAM maximum.

capoeira commented on 2021-02-16 15:51

then could it be my aur helper? I use pikaur