That issue isn't "really" a bug--maybe an oversight. There are a couple of ways to get around this issue. The developer could recompile using an older distro that supports the older libraries, or you could wait until Debian catches up. I really like all that Debian offers, and I like how flexible it is. If you were willing, you could upgrade to Debian Testing, and follow the current track through to the next stable version. Things are far enough along that you'll likely not see to many problems. Your system would then be following a much newer track, and that library will likely be the version you need in Debian Testing. So, even though I don't really think the issue is a bug, there are some options to get around the problem.DuX wrote: ↑Fri Aug 19, 2022 4:06 pm Love your plugins BK! d=:)
However, I've got a little bug report regarding Linux compatibility. In Debian Linux 10 I only get Erosion and Frequency Splitter VST3 to appear in Reaper 6.66. It is progress though, because this is the first time I get any of your plugins appear in Linux Reaper [since 1.7.1]. Could be that Debian 10 uses some older version of libs your plugins need. Interesting that these two work. You'll probably know what's up.
Reaper is getting CLAP support soon, so I'll give the CLAP versions a go, but I doubt they're gonna work since you probably used same newer libraries for compiling. I do use [very sparingly] a W7 laptop on the side so I can run your plugins there. Thank you!
edit: Thanks to xwindows debugger, I found out that your plugins look for GLIB C Library version 2.29 to run. Here's the line for bkChannelTool.so:
swell: dlopen() failed: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/******/.vst3/bkFX/bkChannelTool.vst3/Contents/x86_64-linux/bkChannelTool.so)
Debian 10 comes with 2.28.10 installed and 11 comes with 2.31. I know I'm going to have to update at some point . How come Erosion and Frequency Splitter don't use the same C library as your other plugins? Weird.
Linux isn't great about forwards compatibility, but due to an immense effort started about 10 years ago to try to avoid breaking APIs/ABIs between major releases, great care is taken to maintain backwards compatibility. So, as long as you aren't using one of the stable/LTS distros, your problem will likely not show up.