From 661b217776f9c7e51e1ff9b311706004c2223c8d Mon Sep 17 00:00:00 2001 From: wolf Date: Fri, 6 Jul 2001 09:06:40 +0000 Subject: [PATCH] Document OSF1 5.3 and cxx 6.3. git-svn-id: https://svn.dealii.org/trunk@4827 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/platforms/dec-osf.html | 2 +- deal.II/doc/platforms/dec-osf5.html | 77 +++++++++++++++++++++++++++++ deal.II/doc/readme.html | 5 +- 3 files changed, 81 insertions(+), 3 deletions(-) create mode 100644 deal.II/doc/platforms/dec-osf5.html diff --git a/deal.II/doc/platforms/dec-osf.html b/deal.II/doc/platforms/dec-osf.html index b4f86f9c12..d4b8d3a49b 100644 --- a/deal.II/doc/platforms/dec-osf.html +++ b/deal.II/doc/platforms/dec-osf.html @@ -12,7 +12,7 @@ -

Installation instructions for DEC OSF V4.0

Installation instructions for DEC OSF1 V4.0

Using DEC's cxx compiler

diff --git a/deal.II/doc/platforms/dec-osf5.html b/deal.II/doc/platforms/dec-osf5.html new file mode 100644 index 0000000000..023b6ffa94 --- /dev/null +++ b/deal.II/doc/platforms/dec-osf5.html @@ -0,0 +1,77 @@ + + + + + + The deal.II Readme -- Installation Instructions + + + + + + + +

Installation instructions for DEC OSF1 V5.x

+ +

+ Installation on DEC (now Compaq) OSF1 succeeded mostly for compilation with + both gcc2.95 and cxx version 6.3. Some issues remain: +

+ We were not able to create functional shared libraries with + cxx; this is most probably due to wrong compilation and link + flags and should be solvable by someone with experience with + cxx. +
+ +
+ Using static libraries and cxx, the step-4 example program + can not be linked. This is due to the fact that it links to + the libraries for both 2d and 3d, and the linker reports + conflicts for multiply defined symbols + __init_sti__tria_cc_776f5f60. These are actually + functions automatically generated by the compiler and used to + initialize the static data objects in the file + tria.cc. As the compiler seems to select the + name of this automatically generated function only based on + the file name, it chooses the same name in both the 2d and + the 3d library, which results in the clash. In effect this + means that it is impossible to link programs statically + against libraries for more than one space dimension at a + time. We do not know how to teach the compiler to choose + names differently. +
+ +
+ When compiled with gcc2.95, the step-4 example programs goes + into an infinite loop, at the very end of the program, even + after the destructors for the two objects in the main + functions have run. Having no access to a debugger, the cause + is unknown. +
+ +
+ The step-5 example program crashes right after start when + compiled with both gcc2.95 and cxx6.3. The cause is unknown. +
+ +
+ In general there seem to be programs that hang after execution + (but are not stopped, they actually need computing time). The + cause is unknown. +
+
- SGI IRIX64 with gcc 2.95.x; -
- DEC OSF on +
- OSF1 V5.3 on Alpha with gcc 2.95.x (the same notes probably also apply to Linux on DEC Alpha) and using DEC's cxx compiler version - 6.0; + 6.3; for older systems with OSF1 4.0 and cxx6.0 please see + this page.
- IBM AIX with IBM's xlC 5.0 compiler. -- 2.39.5