For those using the new OS X Lion binaries we are now compiling -- package macosx_10.7_Intel_64.tgz -- you need to be aware that the binaries come with several library files (*.dylib) that are needed for these programs to run. Lion will look for these libraries in the same directories from which they were linked to when I compiled the AFNI programs on our Lion build machine here. But it won't find them there, since these are not standard libraries installed by Apple.

To fix this, you must set the environment variable DYLD_LIBRARY_PATH to the name of the directory where you installed the AFNI binaries. For example, on my test system for Lion (which is not the compile system), I install the binaries in my home directory under a sub-directory named 'abin'. So I set DYLD_LIBRARY_PATH to $HOME/abin -- since I use the tcsh shell, I do this in my $HOME/.cshrc file with a line

setenv DYLD_LIBRARY_PATH $HOME/abin

If I used bash (shudder of repulsion goes here), then I would put this line in my $HOME/.bashrc file

export DYLD_LIBRARY_PATH=$HOME/abin

If you use some other shell (shrug of confusion goes here), you'll have to figure out what to do to set things up so that DYLD_LIBRARY_PATH is properly configured when you login.

If you don't do this, you'll get various messages (depending on which AFNI program you try to run), such as

% 3dAllineate -help
dyld: Library not loaded: /usr/local/lib/libgomp.1.dylib
  Referenced from: /Users/rwcox/abin/3dAllineate
  Reason: image not found
Trace/BPT trap

Unfortunately, I don't have static (*.a) version of these libraries, or I would link to those to save you this annoyance -- since in that case, copies of the needed functions would be directly loaded into the relevant AFNI binaries. I linked statically as far as possible, but ended up having to copy some extra dynamic libraries over into the Lion binaries archive -- thus the need for you to do this extra step. Hopefully just once.

-- ADVANCED USAGE SITUATION --
It is possible you have some other software package installed that also needs you to set DYLD_LIBRARY_PATH to one of its directories. If so, then you need to set this variable to be the list of library directories needed with colons ':' as separators, as in

setenv DYLD_LIBRARY_PATH $HOME/afnibin:$HOME/zorkonbin

It is also remotely possible that the AFNI *.dylib and the other software system have libraries that conflict with each other. In that case, you'll have to complain loudly (but very politely).