Changes between Version 7 and Version 8 of ParallelIPPvers

Timestamp:

May 14, 2009, 2:02:19 AM (17 years ago)

Author:

Sebastian Jester

Comment:

Updated instructions for pschecklibs -force build

ParallelIPPvers

@@ -31 +31 @@
 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.
 
-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"?]
+To run pantasks, your startup file ~/.bashrc or ~/.tcshrc needs to execute psconfig; see [wiki:Pantasks_FAQ#Whyaremynodesdownorresp]
 
-== Setting the IPP version oto use ==
+== Setting the IPP version to 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
@@ -43 +43 @@
 on the command-line.
 
-'''Important:''' To use multiple hosts in parallel in pantasks, your startup file needs to call psconfig. If you do that, there is an [http://pan-starrs.ifa.hawaii.edu/bugzilla/show_bug.cgi?id=1079 unfortunate bug in IPP (1079)] that will break at least the ''man'' command, and maybe more.
+'''Important:''' To use multiple hosts in parallel in pantasks, your startup file needs to call psconfig. If you do that, there is an unfortunate bug in IPP ( #1079 ) that will break at least the ''man'' command, and maybe more.
 
 == Setting up individual config files ==
@@ -82 +82 @@
  # Get IPP (here from svn, by date)
  cd /IPP/
- svn export -r {2009-04-14} https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/ ./svn-20090414
+ svn export -r {2009-05-14} https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/ ./svn-20090514
  # If downloading a numbered tarball, unpack it into a directory 
  # with a corresponding name, like /IPP/ipp-2.6.1. The extlibs and extperl
@@ -89 +89 @@
  
  # Set psconfig id of new version
- psconfig svn-20090414
- # Install autoconf >= 2.61 which is needed - copy it from /IPP/extlibs/autoconf-2.61.tar.gz 
+ psconfig svn-20090514
+ # Point to where CFITSIO will be
+ export CFITSIO=/IPP/svn-20090414.lin64/
+ 
+ # For IPP versions created 2009-05-13 or earlier, install autoconf-2.61 by hand if you don't have it
+ # or a higher version - copy it from /IPP/extlibs/autoconf-2.61.tar.gz 
  # or get it from http://www.gnu.org/software/autoconf/
  cd /IPP/extlibs/autoconf-2.61
  ./configure --prefix=/IPP/svn-20090414.lin64/
  make && make install
- # Point to where CFITSIO will be
- export CFITSIO=/IPP/svn-20090414.lin64/
+ # Now jump down to "Compile and install IPP"
+
+ # IPP versions created 2009-05-14 or later contain autoconf, automake, libtool, pkgconfig in extlibs
+ # For those, make sure that you have the correct versions, ESPECIALLY ON MACS, by force building them
+ cd /IPP/svn-20090514/psconfig/
+ # Force creation of psconfig.csh in current directory
+ psbuild -bootstrap .
+ # These env variables upset libtool if set
+ unset U
+ unset D
+ # Build "build" autotools
+ pschecklibs -force build
+
  # Compile and install IPP
- cd /IPP/svn-20090414/psconfig/
+ cd /IPP/svn-20090514/psconfig/
+ # (if you're not already there)
  psbuild -dev -extbuild 
  # omit the -dev if building from a version-numbered tarball
  # add -clean -rebuild on recompiling to make sure that earlier versions are cleaned
+ # and installation target directories reset.
 }}}
 
-If using pantasks, update your <code>~/.bashrc</code> (or equivalent) to point to the new version. Done!
+If using pantasks, update your <code>~/.bashrc</code> (or equivalent) to point to the new version, and make sure that you can ssh to other machines and call IPP commands there without entering a password (see [wiki:Pantasks_FAQ#Whyaremynodesdownorresp]).
+
+Done!
 
 === To use ippMonitor ===