Changes between Version 3 and Version 4 of Installing_IPP_FAQ

Timestamp:

May 5, 2009, 10:48:55 AM (17 years ago)

Author:

Sebastian Jester

Comment:

more pschecklibs -force build and some reformatting

Installing_IPP_FAQ

@@ -14 +14 @@
 This is the most painless way I found to build all dependencies in Heidelberg:
 
-# Download appropriate extlibs and extperl tarfiles from http://pan-starrs.ifa.hawaii.edu/project/IPP/software/
-# Unpack both in your IPP root directory, i.e. in the same directory where you unpacked the ipp-2.6.1.tgz (or whatever) tarball. In Heidelberg, it's called /IPP
-# Then 
+ 1. Download appropriate extlibs and extperl tarfiles from http://pan-starrs.ifa.hawaii.edu/project/IPP/software/
+ 1. Unpack both in your IPP root directory, i.e. in the same directory where you unpacked the ipp-2.6.1.tgz (or  whatever) tarball. In Heidelberg, it's called /IPP
+ 1. Then 
 {{{
  cd /IPP/ipp-2.6.1/psconfig
@@ -23 +23 @@
 }}}
 
-== The CFITSIO perl module doesn't build ==
+== The CFITSIO perl module doesn't build, or some part of IPP complains about cfitsio missing, but it's installed! ==
 
-I found I needed to set an environment variable CFITSIO to the location of CFITSIO if it's non-standard, e.g.
+I found I needed to set an environment variable CFITSIO to the location of CFITSIO if it's non-standard, e.g. inside the IPP install tree (including if pschecklibs / psbuild  put it there...)
 
 {{{
  # for bash:
- export CFITSIO=/IPP/ipp-2.6.1.lin64/lib
+ export CFITSIO=/IPP/ipp-2.6.1.lin64/
  # for csh:
- setenv CFITSIO /IPP/ipp-2.6.1.lin64/lib
+ setenv CFITSIO /IPP/ipp-2.6.1.lin64/
 }}}
 
@@ -46 +46 @@
 }}}
 
-[http://pan-starrs.ifa.hawaii.edu/bugzilla/show_bug.cgi?id=993 Bug 993] asks for a fix inside the build system.
+#993 asks for a fix inside the build system; as above, `pschecklibs -build force` is the brute-force solution.
 
 == libtool says some library "was moved", but I didn't move anything! ==
@@ -64 +64 @@
 }}}
 
-etc. before you psbuild.
+etc. before you psbuild. (At least some of these are now unset by psbuild automatically.)
 
 http://markmail.org/message/sinepfpepgj7tdff seems to have the real solution for the remaining cases:
@@ -86 +86 @@
 in the install tree, and the dependency_libs was the problem.
 
-I have no ideas how where or when these get set wrongly by libtool, but it seems to be a common bug in libtool.
+I have no ideas how where or when these get set wrongly by libtool, but it seems to be a common bug in libtool. Again, these might be fixed by forcing installation of the autotools versions that are now in extlibs (see comment:ticket:1143:2), again with `pschecklibs -force build`.
 
 == DBD::mysql build error: "CPU you selected does not support x86-64 instruction set" ==
@@ -109 +109 @@
 }}}
 
-The <code>-m32 -march=i386</code> indicate that MySQL was built for 32-bit machines.  Furthermore, the fact that the include files are being sucked in from <code>/usr/include/mysql</code> indicates that it's trying to use the system version, rather than one we've installed ourselves.
+The `-m32 -march=i386` indicate that MySQL was built for 32-bit machines.  Furthermore, the fact that the include files are being sucked in from `/usr/include/mysql` indicates that it's trying to use the system version, rather than one we've installed ourselves.
 
 The solution is to force MySQL to build:
@@ -120 +120 @@
 == libjpeg fails make ==
 
-libjpeg fails the <code>configure</code> script, or <code>make</code>, and <code>pschecklibs</code> reports:
+libjpeg fails the `configure` script, or `make`, and `pschecklibs` reports:
 {{{
 problem building libjpeg : failure in make
@@ -126 +126 @@
 
 
-libjpeg is an old library, and the bundled files for running the <code>configure</code> script pre-date several systems (e.g., Mac OS X, 64-bit Linux machines).  You can get around this by going into the directory containing libjpeg and doing:
+libjpeg is an old library, and the bundled files for running the `configure` script pre-date several systems (e.g., Mac OS X, 64-bit Linux machines).  You can get around this by going into the directory containing libjpeg and doing:
 {{{
 % cp /usr/share/libtool/config.guess .