MacOSX for Unix geeks?!?

rhg said:
Do an echo $PATH in the xterm to see what the PATH is set to. If it doesn't contain /sw/bin you probably didn't source (i.e. execute in the calling shell context by putting a . in front of the script) the /sw/bin/init.sh script in .profile:
. /sw/bin/init.sh

Actually I had/have . /sw/bin/init.sh in the .profile, but it did not do any good. On the other hand, you were right about the $PATH (how come I didn't check it ;(!!!), so a 'export PATH=$PATH:/sw/bin' in the xterm fixed the problem. I will have to look into the init.sh, to see what is supposed to do, but I can also manually append /sw/bin to the PATH, anyway ... good ... thank you!
 
Back
Top