Issue with Mac OS Catalina

[donaldhamby]

Hi all,

I've recently upgraded to Mac OS Catalina, but I'm getting the following error when I try and run a patch

Any ideas how I might fix this?

Thanks in advance!

[jaffasplaffa]

Did you try the good old trick:

Rich click the app and select open?

[donaldhamby]

Just tried that, but unfortunately it didn't work! Thank you for the suggestion though

[jaffasplaffa]

Oh, thought it might work.

Problem is that Catalina has new rules regarding security. As I understand it, Apple needs to verify pretty much every single app, or else they can't be used on Catalina and up. My guess is that Johannes have not looked into this yet. I have not read the details though so not 100% sure how it works.

But there is a great article about Catalina and music software here. Maybe you can find a solution there:

macOS Catalina will be incompatible with much of your music software; here's...

[donaldhamby]

I just tried reinstalling, and the right-click method works to get the main app running, but unfortunately the error comes up when I try to run a patch

My knowledge of software is very limited, but is there maybe a way to verify the "make" component on a desktop level, before running the main Axoloti software?

[jaffasplaffa]

My knowledge of software is very limited, but is there maybe a way to verify the "make" component on a desktop level, before running the main Axoloti software?

Sorry, that I have no idea about. We can try and tag some of the more code savy people in this forum:
@johannes @thetechnobear @urklang @SmashedTransistors @lokki @SirSickSik

[donaldhamby]

Thank you, any help much appreciated!

[jaffasplaffa]

Yeah, I think some things need to be done for Catalina support for Axoloti.

And that is @johannes who works on that stuff and he is rarely around. So not sure what the future perspective for this is for Catalina support.

If it was me, I would not have done the Catalina update yet. But now you have done it, I guess you need a solution of some sort

[donaldhamby]

Indeed, but hopefully there's a simple solution!

[janvantomme]

Can you post the error you are getting here? Might be useful to find out what's happening.

I usually stay one release behind on macOS. Still on High Sierra now, haven't bothered upgrading to Mojave yet.

[donaldhamby]

No problem

The pop up says:

Also get the following in the console:

[urklang]

I think what's happening here is that calling the make utility from the command line is just failing because of OS X's draconian security mechanisms. If I recall correctly, make is part of the "Command Line Tools" package which is distributed by Apple themselves.

Try opening the Terminal app and just typing in the command make and pressing enter. It should give you something like:

make: *** No targets specified and no makefile found. Stop.

which just means that the program is available and tried to run but it didn't haven't any input to work with which is normal.

If this gives you any kind of security verification dialog, authorize the program. If it fails to find the application, try running the command:

which make

to see if it can find make. On my my virtual machine OS X this gives:

/usr/bin/make

which is where the actual make binary is installed.

Another approach is to try installing the Command Line Tools: https://medium.com/faun/macos-catalina-xcode-homebrew-gems-developer-headaches-cf7b1edf10b7

The new way to do this seems to be:

xcode-select --install

After they're installed check that the make program is visible and working using the same ideas I describe above. At that point the Axoloti patcher app should be able to call it.

[donaldhamby]

Thank you for the suggestion

I'm not getting any kind verification dialogue if I enter the above into the terminal

I have xcode installed, but that hasn't made any difference

I think the 'make' in this instance is something installed with Axoloti, the error message I'm getting says "Firefox downloaded this file today at 09:47 from github.com"

Don't know if that helps at all?

[tele_player]

Yes, the ‘make’ used by Axoloti patcher is part of the axoloti_runtime.

[urklang]

Ah ha, I had forgotten that make is packaged in. I'm guessing that you'll hit similar errors with the compiler toolchain that Axoloti fetches. Let me see if I can come up with a workaround.

[donaldhamby]

Thank you, that’s much appreciated!

[urklang]

Can you go into your axoloti directory and then into the platform_osx/bin directory?

Run ls -lat from that directory and paste the output here.

Then try directly executing the downloaded make executable from that directory and see if it triggers a verification dialog:

./make

By the way, if you jump on Discord here I can walk you through it live: https://discord.gg/VhHbGfr

See this Apple post about force opening apps on Catalina: https://support.apple.com/en-us/HT202491

Scroll down to "How to open an app that hasn’t been notarized or is from an unidentified developer" We need everything in platform_osx/bin to be flagged as safe to execute.

[donaldhamby]

OK, this is making sense. I’ve got make working and as you say, it’s now flagging more files that need to be verified. I’ve verified five so far, but I’ll have to finish the job later as I need to go out soon!

Thank you for your help, I’ll try and do the rest of the problem files later tonight and let you know if it works

[tele_player]

I think it's a total of about 11 executables. (EDIT: no, it's more than that)

I've been considering installing the Catalina update, I'm glad this issue has a reasonable solution.

[donaldhamby]

OK, worked my way through everything, and it's all working now! Thank you @urklang for helping me through this, such a relief!

One extra point for anyone trying this, most of the files were exec files, so could be opened in the terminal, with the exception of liblto_plugin.so, which I got around by opening in TextEdit