David Niemi wrote:
On Wed, 2005-08-31 at 07:12 +0100, Paul Howarth wrote:
On Tue, 2005-08-30 at 22:26 -0400, David Niemi wrote:
************ Excerpt from Install Instructions
script (install.sh) creates compiler environment script files
(ifortvars.sh/idbvars.sh) that set these variables. It is strongly
recommended that you add those script files into your login script
source the script to setup the compiler environment:
* > source <install-dir>/bin/ifortvars.sh(.csh)
to use ifort
* > source <install-dir>/bin/idbvars.sh(.csh)
to use idb
******************
Should I put the paths to the script files in my .bash_profile or
in /etc/profile so that all users (me) can use it?
What's in these files? Do they have conflicting settings for any of the
variables (i.e. if you run both, can you then use both products without
needing to run either script again?)?
These scripts just put in the path to the compiler and debugger into the
path statement and add a couple environment variables.
PATH="/opt/intel/fc/9.0/bin:$PATH"; export PATH
LD_LIBRARY_PATH="/opt/intel/fc/9.0/lib:$LD_LIBRARY_PATH"; export
LD_LIBRARY_PATH
MANPATH="/opt/intel/fc/9.0/man:${MANPATH}"; export MANPATH
with if statements to find the status / existence of the variables.
Yes, the first thing I did was inspect the scripts to see what they did
before even thinking of running them.
If they don't conflict, the best place is probably in /etc/profile.d,
where the settings will be picked up automatically by all users.
After putting the path and script name into the profile.d, should I log
out and back in again for it to take effect, or?
The scripts seem to be sane and not clobber anything, so I'd put them in
/etc/profile.d
You will need to log out and then back in again for them to take effect.
I found the following site for checking the environment settings
http://www.comptechdoc.org/os/linux/usersguide/linux_ugenvironment.html
That site doesn't explicitly mention /etc/profile.d, but if you look in
/etc/profile, you'll see that that script runs all the scripts within
/etc/profile.d itself.
Cheers, Paul.
