Changes between Version 5 and Version 6 of ParallelIPPvers

Timestamp:

Apr 14, 2009, 4:25:16 AM (17 years ago)

Author:

Sebastian Jester

Comment:

clean up PSCONFDIR-related things

ParallelIPPvers

@@ -1 +1 @@
 = How to install one or more parallel IPP installations =
 
-== Preliminaries: Setting up a global psconfig directory ==
+IPP comes with a mechanism called 'psfconfig' that intends to allow installation and compilation of multiple versions and for multiple platforms on the same disk area. A user selects one of the installed versions (e.g. ipp-2.6.1) by issuing a psconfig command, e.g.
+{{{
+ psconfig ipp-2.6.1
+}}}
+which then sets the PATH etc. appropriately to point to the relevant directories for the chosen version and architecture. The psconfig mechanism needs just a little bit of setting up.
+
+== Preliminaries: Setting up a global psconfig directory before installing IPP for the first time ==
 
 There's one directory where all IPP installations live. By default, it's ~/psconfig/ but you can make it a different location by creating a file ~/.psconfigrc which contains
@@ -9 +15 @@
 }}}
 
-Then create a directory $PSCONFDIR/psconfig and copy the psconfig.bash and psconfig.csh scripts there from the source tree (this is something that the build/install will probably do automatically in future).
-
-The only thing that's missing is an alias for psconfig that reads those .csh or .bash files:
+'''If someone else has installed IPP for you''', as is the case in Heidelberg, creating that file is all you need to do to point to those IPP installations. Then set the required aliases in your .[t]chsrc or .bashrc file:
 
 {{{
  bash: alias psconfig='source /IPP/psconfig.csh'
- csh:  alias psconfig "source /IPP/psconfig.bash"
+ [t]csh:  alias psconfig "source /IPP/psconfig.bash"
 }}}
+(or whatever else PSCONFDIR is set to instead of /IPP).
+
+If you are doing the installing of IPP, the PSCONFDIR root directory is set up by the command
+{{{
+ psbuild -bootstrap $PSCONFDIR
+}}}
+'''be sure to use the same value for PSCONFDIR here as in the ~/.psconfigrc''' or everything will get messed up. Once installed, psconfig will set an environment variable PSCONFDIR automatically. (See installation instructions below for where to find psbuild...)
 
 Alternating between versions installed in a global directory and versions installed in your own home directory is possible, but you need to unset PSCONFDIR, make sure that there's no .psconfigrc (e.g. by renaming it), and point psconfig at the different different directory, so I don't recommend it.
@@ -22 +33 @@
 To run pantasks, your startup file ~/.bashrc or ~/.tcshrc needs to execute psconfig; see [wiki:Pantasks_FAQ#Why_are_my_nodes_"down"_or_"resp"? Pantasks_FAQ#Why are my nodes "down" or "resp"?]
 
-== Setting an alias ==
-
-If ipp was installed with
-
-{{{
- psbuild -bootstrap PSCONFDIR
-}}}
-
-the psconfig.bash and psconfig.csh point to the IPP installations in PSCONFDIR by default. Thus, for other users to use a given IPP install, they just need to create the same psconfig alias as the person who installed IPP, i.e.
-
-{{{
- alias psconfig="source PSCONFDIR/psconfig.bash"
-}}}
-
-for bash, or
-
-{{{
- alias psconfig "source PSCONFDIR/psconfig.csh"
-}}}
-
-for [t]csh.
-
-PSCONFDIR needs to be readable by all the intended users, of course, '''AND NEEDS TO BE IDENTICAL TO WHAT'S SET IN ~/.psconfigrc'''.
+== Setting the IPP version oto use ==
 
 In Heidelberg, there's always a softlink ipp-default pointing to the most recent installed version of IPP. To use that, then just issue the command