SRT for Release 1.2.0

29 Aug 1996
Related pages: [BaBar Home Page] [Computing]

Table of Contents:

• Changes in SRT for Release 1.2.0
• What user should do for Release 1.2.0
• How to add BFARCH into PATH of SRT.

Change of SRT in Release 1.2.0

* There is a new SRTstartup.csh script, which users should
  eventually copy and use (see below).  It will set BFARCH
  differently from the old one on AIX 3.* systems (where it
  will be set to AIX3 instead of AIX2) and HP-UX 9 systems
  (where it will be set to HP-UX9 instead of HP-UXA).

* The .mk and GNUmakefiles have been changed to only compare
  on the first characters of BFARCH.  For example, AIX3 and
  AIX4 will be treated the same.  Although it may be eventually
  required to change this in specific cases, this allows us
  to start test build on AIX4 and HP-UX10.

* The main (release top level GNUmakefile) will convert
  BFRACH from AIX2 to AIX3, and HP-UXA to HP-UX9, if it
  sees them.

What do users have to do for Release 1.2.0

1) If they are using only release 1.2.0 and later as test
releases, they should copy and use the new SRTstartup.* script(s).
This will then allow them to use later OS versions than
OSF1 3.1, AIX 3.2 and HP-UX 9 when the support becomes
available.

2) If they _are_ using releases older than 1.2.0, they
should _not_ use the new SRTstartup.csh until they are
in state (1).  Regretably, this means they cannot use the new
architecture support, and they should stay on AIX 3.*
and HP-UX 9 systems.

Careful people can keep both SRTstartup.* scripts around and
use then appropriately, or manually set BFARCH to the right values.
These are:
a) only AIX2 or HP-UX9 for releases before 1.2.0
b) AIX3, AIX4, etc or HP-UX9, HP-UX10, HP-UX11 at or after
   release 1.2.0

How to add new BFARCH into PATH

  If you still use old SRTstartup.csh and need to run binary from
new BFARCH such as AIX3, or if you are using new SRTstartup.csh and need
to run newer BFARCH such as AIX3-2.7.2, please read on.

  First check if the new BFARCH is in your PATH. Type 'echo $PATH' to check
your PATH. For example, to use release 1.2.0, architecture AIX3, then
make sure $BFDIST/releases/1.2.0/bin/AIX3 is in the $PATH. Further more,
one can type 'which newrel' to see if the PATH is set up properly.

  If the PATH is not set up properly, one can use SRTpath.csh to set it up.
For instance, to use binaries from AIX3-2.7.2, release 1.2.0: 

   |*  setenv BFARCH AIX3-2.7.2
   |*  source $BFBING/SRTpath.csh 1.2.0
   |*  (or source $BFDIST/releases/newest/SoftRelTools/SRTpath.csh 1.2.0) 

   SRTpath.csh will take the value of architecture from $BFARCH, and add 
./bin/$BFARCH and $BFDIST/releases/1.2.0/bin/$BFARCH to PATH.

   One can also use '-a arch' option to run binaries from one architecture 
while developing codes for another architecture. For instance, to develop 
code for AIX4, leave AIX4 in BFARCH, then type:

   |*   source $BFBING/SRTpath.csh -a AIX3-2.7.2 1.2.0

   It adds ./bin/AIX3-2.7.2 and $BFDIST/releases/1.2.0/bin/AIX3-2.7.2 
to PATH, but BFARCH remains AIX4. See man page