From 609c0e6b6ccb23a4568d6d0ef71318d85455fac1 Mon Sep 17 00:00:00 2001
From: wolf
+ deal.II works without problems with shared
+ libraries on this platform, if you list the paths
+ Installation instructions for SGI IRIX
+
+ $D/base/lib
, $D/lac/lib
, and
+ $D/deal.II/lib
in your $LD_LIBRARY_PATH
+ environment variable, where $D
is the path to your
+ installation of the deal.II library. The
+ necessary actions can be done with the commands
+
+
+ for csh-like shells, or by
+
+ setenv LD_LIBRARY_PATH $D/base/lib:$D/lac/lib:$D/deal.II/lib:$LD_LIBRARY_PATH
+
+
+
+ if you use the ``bash'' shell. Please substitute
+ export LD_LIBRARY_PATH=$D/base/lib:$D/lac/lib:$D/deal.II/lib:$LD_LIBRARY_PATH
+
+ $D
+ by whatever is the appropriate path on your installation.
+
+ These actions are necessary, since on SGI IRIX it seems not + possible to link a program to a shared library by giving the full + path of the latter. On all other systems where we use shared + libraries, the full path to the shared library is given on the + command line and stored somewhere in the executable, so that the + linker finds the library irrespective of the fact that the path is + specified in LD_LIBRARY_PATH or not. However, on SGI IRIX, as it + seems, only the library's name, not its path seems to be stored in + the executable, so LD_LIBRARY_PATH has to be modified. +
+ ++ We note that this might lead to problems if, for whatever reason, + you have multiple versions of deal.II installed + and compiled with different flags; then, to ensure that you link + to the correct library at execution time, you will have to + redefine LD_LIBRARY_PATH before execution of your program. Another + possibility would be to used statically linked libraries instead + of shared ones (see the + ReadMe file to + find out how to do that). +
+ + + + diff --git a/deal.II/doc/readme.html b/deal.II/doc/readme.html index 4b7b560b73..8ad1dfcd76 100644 --- a/deal.II/doc/readme.html +++ b/deal.II/doc/readme.html @@ -35,7 +35,6 @@