I'm new to Solus. I'm so new I haven't even installed it yet on my main computer (I have it installed on another computer for test purposes). While I am a Linux newbie, I am not a programming newbie. I first migrated to Linux about one year ago, but since I'm a Linux newbie I had no idea which version of Linux I should get, so I tried Deepin, but it had no forum support and almost no apps I could use in their storefront, so I tried Synaptic, which like APT, trashed my system due to "dependency hell". That's when I learned the value of a storefront (among other things). I've now been through three more Linux flavors since then, and I've finally decided I want to migrate permanently to Solus. Being a programmer/developer, I decided to work with GTK4, but it has major issues that weren't resolved until after 4.14, so that's one (of many) reasons I decided on Solus. A different issue I ran into that no one seems to be able to solve, is my custom apps wouldn't run on any version of Linux until I typed:
sudo ln -sT /lib64/ld-linux-x86-64.so.2 /lib/ld64.so.1
That was so I could create a symbolic link to ld-linux-x86-64.so.2 -- which worked, but the problem is this isn't an actual solution because if someone else wants to run my exe (is that what you call it?) on their Linux computer, the exe will fail to run unless they enter that same command line as above. So a real fix would be for me to tell the linker to force my exe to use ld-linux-x86-64.so.2 instead of the default libc.so.6 library (something else that doesn't make sense to me yet). I tried the following ld command line arguments:
-Ild-linux-x86-64.so.2
-dynamic-linker=ld-linux-x86-64.so.2
But that doesn't work. Any ideas?
