| 1 |
608 |
ributzka |
Installing Open64
|
| 2 |
|
|
=================
|
| 3 |
|
|
|
| 4 |
|
|
|
| 5 |
|
|
Introduction
|
| 6 |
|
|
------------
|
| 7 |
|
|
|
| 8 |
|
|
This document explains how to compile and install Open64 on a Itanium based
|
| 9 |
|
|
system. The documentation is split into 5 steps:
|
| 10 |
|
|
|
| 11 |
|
|
* Prerequisites
|
| 12 |
|
|
* Obtaining the Source Code
|
| 13 |
|
|
* Compiling
|
| 14 |
|
|
* Environment Variables
|
| 15 |
|
|
* Installation
|
| 16 |
|
|
|
| 17 |
|
|
We encourage you to pay attention to the Prerequisites in order to avoid un-
|
| 18 |
|
|
necessary problems later in the build process. Should you ever encounter any
|
| 19 |
|
|
problems with one of the steps, please take a look in the FAQ, the forum or
|
| 20 |
|
|
leave a comment on our web site http://www.open64.net.
|
| 21 |
|
|
|
| 22 |
|
|
|
| 23 |
|
|
Prerequisites
|
| 24 |
|
|
-------------
|
| 25 |
|
|
|
| 26 |
|
|
In order to compile Open64 successfully, you should meet the following
|
| 27 |
|
|
requirements:
|
| 28 |
|
|
|
| 29 |
|
|
* Linux based OS
|
| 30 |
|
|
Currently, Open64 is only intensively tested on Linux/IA64.
|
| 31 |
|
|
|
| 32 |
|
|
* Itanium based machine
|
| 33 |
|
|
In this release, Open64 is only supported and tested for the Itanium 2
|
| 34 |
|
|
architecture. Itanium 1 is supported, but not tested.
|
| 35 |
|
|
|
| 36 |
|
|
* GNU Make
|
| 37 |
|
|
You should use a up to date version of Make. Unfortunately the current GNU
|
| 38 |
|
|
Make version 3.81, which is shipped with the latest Linux distributions,
|
| 39 |
|
|
causes some trouble--this version leads to a Makefile error. To solve this
|
| 40 |
|
|
problem, just run the Makefile again and the error will not appear. To
|
| 41 |
|
|
avoid this error, please install GNU Make version 3.80. This version has
|
| 42 |
|
|
been tested and works with our Makefile.
|
| 43 |
|
|
|
| 44 |
|
|
* GCC (GNU Compiler Collection)
|
| 45 |
|
|
In order to compile the Open64 source code, you need GCC 3.2.x - 3.4.x.
|
| 46 |
|
|
Support for GCC 2.x has been dropped since release 1.0 and is not yet
|
| 47 |
|
|
available for GCC 4.x. If you don't have any of the suggested GCC versions
|
| 48 |
|
|
above, we recommend that you to install GCC 3.4.6.
|
| 49 |
|
|
Open64 has been tested and successfully compiled with GCC 3.3.x and 3.4.x.
|
| 50 |
|
|
|
| 51 |
|
|
* IFC (Intel Fortran Compiler)
|
| 52 |
|
|
To compile and use the Open64 Fortran compiler, you need to install the
|
| 53 |
|
|
Intel Fortran Compiler. A free version for noncommercial use is available
|
| 54 |
|
|
from Intel.
|
| 55 |
|
|
(http://www3.intel.com/cd/software/products/asmo-na/eng/download/download/index.htm)
|
| 56 |
|
|
|
| 57 |
|
|
Depending on the path where you have installed IFC, you may have to adapt
|
| 58 |
|
|
the Open64 Makefile. Please go to open64/kpro64/linux/make/gcommondefs and
|
| 59 |
|
|
check the defines for F90 and F90_RTLIBS and adjust them if necessary.
|
| 60 |
|
|
Please also add the path to the IFC libraries to your library path.
|
| 61 |
|
|
|
| 62 |
|
|
export LD_LIBRARY_PATH=/path/to/IFC/lib:$LD_LIBRARY_PATH
|
| 63 |
|
|
|
| 64 |
|
|
|
| 65 |
|
|
Obtaining the Source Code
|
| 66 |
|
|
-------------------------
|
| 67 |
|
|
|
| 68 |
|
|
To compile Open64 you need to obtain the source code first.
|
| 69 |
|
|
|
| 70 |
|
|
There are two ways:
|
| 71 |
|
|
|
| 72 |
|
|
* Obtain the Source Code as Archive
|
| 73 |
|
|
You can download the source code from Sourceforge.net
|
| 74 |
|
|
You will find the links to the different versions in our download section.
|
| 75 |
|
|
(http://www.open64.net/download.html)
|
| 76 |
|
|
|
| 77 |
|
|
You have to obtain the source code and the prebuild libraries/binaries!
|
| 78 |
|
|
|
| 79 |
|
|
Extract the source code and the prebuild binaries/libraries
|
| 80 |
|
|
|
| 81 |
|
|
tar xzf open64-2.0.tar.gz
|
| 82 |
|
|
tar xzf open64-2.0-prebuild.tar.gz
|
| 83 |
|
|
|
| 84 |
|
|
* Obtain the Source Code from our Subversion Repository
|
| 85 |
|
|
You can also obtain the latest version of our source code from the sub-
|
| 86 |
|
|
version repository.
|
| 87 |
|
|
To get the latest version issue the following command:
|
| 88 |
|
|
|
| 89 |
|
|
svn export https://svn.open64.net/svnroot/open64/trunk open64
|
| 90 |
|
|
|
| 91 |
|
|
This will copy the latest code to the directory open64.
|
| 92 |
|
|
|
| 93 |
|
|
You can also surf through our subversion repository online.
|
| 94 |
|
|
(http://svn.open64.net)
|
| 95 |
|
|
|
| 96 |
|
|
You also need to obtain the prebuild libraries/binaries and extract them
|
| 97 |
|
|
to the root directory of the Open64 source code.
|
| 98 |
|
|
|
| 99 |
|
|
|
| 100 |
|
|
Compiling
|
| 101 |
|
|
---------
|
| 102 |
|
|
|
| 103 |
|
|
Switch to the Open64 directory and execute the following command:
|
| 104 |
|
|
|
| 105 |
|
|
gmake all -f Make.native
|
| 106 |
|
|
|
| 107 |
|
|
If you want to build a debugable version of Open64, please use the following
|
| 108 |
|
|
command:
|
| 109 |
|
|
|
| 110 |
|
|
gmake all BUILD_OPTIMIZE=DEBUG -f Make.native
|
| 111 |
|
|
|
| 112 |
|
|
|
| 113 |
|
|
Environment Variables
|
| 114 |
|
|
---------------------
|
| 115 |
|
|
|
| 116 |
|
|
Before the installation, and later when you want use Open64, the environment
|
| 117 |
|
|
variable TOOLROOT should always be set.
|
| 118 |
|
|
|
| 119 |
|
|
Depending on whether you are root or a user add the following lines to your
|
| 120 |
|
|
/etc/bashrc or ~/.bashrc:
|
| 121 |
|
|
|
| 122 |
|
|
export TOOLROOT=/opt/open64 or
|
| 123 |
|
|
export TOOLROOT=/home/{user name}/local/open64 or
|
| 124 |
|
|
export TOOLROOT=/somewhere/you/have/write/permission
|
| 125 |
|
|
|
| 126 |
|
|
This defines where to install the Open64 and where later Open64 has to search
|
| 127 |
|
|
for libraries and binaries.
|
| 128 |
|
|
|
| 129 |
|
|
You should also add the Open64 binary directory to you path.
|
| 130 |
|
|
|
| 131 |
|
|
export PATH=$TOOLROOT/usr/bin:$PATH
|
| 132 |
|
|
|
| 133 |
|
|
Don't forget to source your updated .bashrc file.
|
| 134 |
|
|
|
| 135 |
|
|
source ~/.bashrc
|
| 136 |
|
|
|
| 137 |
|
|
Warning!!!
|
| 138 |
|
|
If you have more the one version of Open64 installed, be aware of the following
|
| 139 |
|
|
fact:
|
| 140 |
|
|
Lets assume that one version is installed in /opt/open64-1 and the other in
|
| 141 |
|
|
/opt/open64-2 and that your TOOLROOT is set to /opt/open64-1. Now, even if you
|
| 142 |
|
|
start Open64 in /opt/open64-2, it will execute Open64 in /opt/open64-1 because
|
| 143 |
|
|
the TOOLROOT is set to this directory.
|
| 144 |
|
|
|
| 145 |
|
|
|
| 146 |
|
|
Installation
|
| 147 |
|
|
------------
|
| 148 |
|
|
|
| 149 |
|
|
We are almost done. Now, you have just to start the install script and Open64
|
| 150 |
|
|
will be installed in the directory defined by the environment variable TOOLROOT.
|
| 151 |
|
|
|
| 152 |
|
|
./INSTALL.native
|
| 153 |
|
|
|
| 154 |
|
|
Congratulations. You have succsessfully installed Open64. Have fun.
|
| 155 |
|
|
|
| 156 |
|
|
Your Open64 Team
|
| 157 |
|
|
|