@update_afni_binaries macos 10.14

AFNI Message Board
1

I’m very confident that I’m simply doing something wrong, but if I run
@update.afni.binaries -defaults -do_extras
Then I get the following error:

– running @update.afni.binaries version 3.16, September 16, 2020
– have AFNI binaries under /Users/tevesjb/abin
– install dir: using existing /Users/tevesjb/abin
– any downloads will be from https://afni.nimh.nih.gov via curl -O -f

– attempting to install package macos_10.15_local_gcc_clang under
install dir: /Users/tevesjb/abin…
– have install dir
deleting old temporary directory…
++ working in new temp dir, .tmp.install
++ getting install prog: curl -O -f bin/misc/@update.afni.binaries …
curl -O -f https://afni.nimh.nih.gov/pub/dist/bin/misc/@update.afni.binaries
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 49104 100 49104 0 0 95719 0 --:–:-- --:–:-- --:–:-- 95719
– fixing lost permissions on @update.afni.binaries
++ using updated @update.afni.binaries, instead…

++ running: tcsh tmp.@update.afni.binaries -no_recur -defaults -do_extras
– running tmp.@update.afni.binaries version 3.19, January 11, 2022
– have AFNI binaries under /Users/tevesjb/abin
– install dir: using existing /Users/tevesjb/abin
– any downloads will be from https://afni.nimh.nih.gov via curl -O -f

– attempting to install package macos_10.15_local_gcc_clang under
install dir: /Users/tevesjb/abin…
– have install dir
deleting old temporary directory…
++ working in new temp dir, .tmp.install
– skipping update of tmp.@update.afni.binaries
++ downloading test file: curl -O -f macos_10.15_local_gcc_clang/afni …
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (22) The requested URL returned error: 404 Not Found

2

I meant to type 10.15, whoops.
What’s the best way to update the binaries for AFNI in this configuration?

3

Hello,

The fact that you are using package macos_10.15_local_gcc_clang suggests that you have done the compiling yourself. There is no such AFNI distribution package, but there is Makefile.macos_10.15_clang which results in that package name.

Does is seem like you are compiling locally on that machine?

  • rick
4

Hm, I don’t remember doing this but I also did it approximately 3/4 of a pandemic ago. Is there any compelling reason not to just build from the tip of the latest master if I feel adventurous?

5

That will actually be the recommended method on M1 macs, at least until some of the signing details get straightened out.
The only downside is that it might not match any exact “official” release. If you care about matching releases, checkout the most recent label and build off of that.

  • rick