Yeah, sorry, should've mentioned the dollar sign, that is usually used to indicate the start of a command run as a user: versus commands run as root (The most privileged user on the system), indicated with a hash: At this point, it looks like your errors are related to your environment not being set up properly. $TCL_LIBRARY should be set to the directory containing the Tcl runtime libraries with: You might want to check /lib/tcl, /usr/lib/tcl, and /usr/local/lib/tcl* for .dynlib files. The same goes for $TK_LIBRARY. Unsure where $SAVI should be pointing to, likely the directory of the .app file (Or somewhere inside that). A little investigating found /usr/local/savi as a potential location. /System/Library/Frameworks/tcl.framework is another potential candidate. If it's not there, you might want to take a look at the output of the make command you ran to build and install the program (Re-running it shouldn't cause any errors, it'll just overwrite the old executable). Alternatively, yeah, you could install Ubuntu on an old computer or run it within a virtual machine. Whenever you feel frustrated enough to give up setting it up on OS X! Hop on IRC if you have more questions, debugging programs like this tends to be easier in real time.$ command
# command
$ export TCL_LIBRARY=/path/to/directory
I'm smart enough to know what the dollar sign means; my problem is I'm too stupid to know what everything else means so I always start by copy-pasting everything I see and working my way backwards. the Ubuntu issue is another thing. I may mess about with it when I get some time. In the meantime, I've capitulated and devoted my debug time to finding a better solution. Four pages buried on Google, I succeeded. Thanks sincerely for your help. I shall not abuse it when I don't need it.
Well, for future learning's sake: "which" finds the location of the its argument, turning "gcc" (The compiler) into "/usr/bin/gcc", "cd" changes the directory, "tar" extracts the archive, and "make" instructs the system to follow the commands laid out in the Makefile, describing how to build and install the package. The "&&"s between each command just serve to conditionally execute them only in the case that the previous command succeeded.