|
From: <rs...@ba...> - 2020-07-04 09:56:33
|
Dear Anthony, I love your humour and am full of awe for your very worthy exploration into the field of computermusic archeology (I am serious, no cheekiness intended). I’d love to see you and Bernard reach your goals! I guess next to letting us know the great news, you want to get a feel how broadly your current achievements apply out in the wild, so here my experience: I have an aged MacBook Pro (mid 2012), 64-bit, but running Catalina, with a hopefully clean, quite recent setup. As you likely know, Apple has lately built in a lot of security blocks to prevent unsigned binaries from running. But these can be bypassed if you know how. So for anybody new to this: If you run ./bp64 (no more 32-bit on Catalina) Apple will telly you it can’t run the binary because it cannot verify it is free of malware (this happens with any unsigned program, so don’t panic). At that point Apple just offers you to delete the binary or ignore the incident. So you need to ignore, and then straightforwardly go to System Apple/System Preferences/Security & Privacy. And if the “general” tab is open, you’ll see a line stating something like “bp64 just tried to take over your computer, we heroically prevented that” - if you now press the button “open anyways” you should be fine to go. Next ./bp64 should just work. And so it does! Other than that I got through you whole list perfectly. Only in the end it gave me an error that it can make no sense of —indian for now (no it doesn’t “autocorrect” two minuses to an em-dash on the commandline :-) ). So I am excited to see this moving again, and am happy to play the occasional guinea pig for being kept in the loop! (btw. I even installed csound through homebrew and was a bit shocked to see it installs no less than, gcc 10, llvm, openjava, Faust and something like 10 more major packages ;-) But homebrew is totally awesome so I trust it’s fine and won’t mess up my system!) Thanks again and best spirits! Rainer |
