Setting up your Compilation Environment

 

Intoduction:
I have spoken with the Administrator of the Suns in the Jennings Lab, and have
come across a few 'wrinkles' to what I said in class on Monday.

Basically, a lot of the cool new programs that are available on the Sun
Workstations aren't in "/usr/local/bin". Instead, they have been installed
into a new directory, which is entitled "/p".

The "/p" directory contains binaries that are platform-dependant. This means
that they will only run on Solaris/SPARC or SunOS/SPARC. Thus, each type
of machine will NFS mount a different directory, at the same place in their
respective filesystem. So, you can, in effect, set your paths up the same
in order to get at the same software (different binaries) on each type of
machine.
What this means to you:
You need to be very careful when setting your path. There are three different
versions of GCC available, and several differnet copies of MAKE and PERL
(for example). This is what I reccommend:

	- Set your PATH to include the following direcories (in order):
		/usr/bin
		/usr/sbin (necessary for ping)
		/p/gcc-2.8.1
		/p/gnu
		/p/perl
		/p/gdb-4.17/bin
		/usr/local/bin
		/usr/ccs/bin
		/usr/ucb
		/usr/openwin/bin
		.

	- Make the following aliases:
		netscape = /p/www/netscape
		ssh = /p/ssh/ssh

		

Basically, you should try and make aliases for whatever is a one-shot deal.
For example, the only binary that you're *ever* going to want to run out
of "/p/www/" is "netscape", so it doesn't make sense to clutter-up your path
with "/p/www". In this instance, an Alias is more efficient.

Information about creating Aliases and PATHS can be found in the documentation
for your shell. I'll post another announcement about this if there are
questions.