ouch... Ive not installed Catalina yet (*)
the runtime is basically just a copy of build tools used for cross platform development, so why is this issue not 'all over the internet' ... surely developers are already running these tools. and Ive not seen discussion from them on authorising all these 'utilities' - and how are things like home-brew working?
(so my suspicion is auth individual binaries is not the solution... )
perhaps it's a 'downloaded' application cannot run non-auth executables, but even there, things like eclipse do this, perhaps all developers have disabled gatekeeper? (seems unlikely)
id be surprised if Xcode-select helps, as its not going to just be make - its going to need to them spawn (from make)the compiler (arm-none-eabi-gcc).
if you to run in the terminal... do they work, or do you get same error?
hmm, more questions that answers , until I can run Catalina.
one idea. I wonder if apple differentiates system software to apps.
I would like to try the following
sudo mv /Applications/axoloti_runtime /usr/local
then in Axoloti->preferences , change runtime dir to /usr/local/axoloti_runtime
then try to compile a patch. (you might need to restart axoloti, not sure )
if thats not working again running individual commands from the terminal might be enlightening.
if it doesn't work you can reverse using:
sudo mv /usr/local/axoloti_runtime /Applications
apart from that, I think Id need to install Catalina to see whats possible.....and how to work around things.
(in particular, Id like to isolate the cause of the issue a little better)
(*) Ive some hardware that doesnt work on it, so I was waiting on them to fix it. so, chicken n' egg , Ive not been able fix/verify software I work on, due to others not having their software fixed
don't have enough spare macs to dedicate one to this, nor enough space to create a VM - arghh