[skabilan]

Hi,

I am trying to install OpenFOAM-1.4.1 on an Itanium machine. foamInstallationTest complains only about

icoFoam *** not installed ***
CRITICAL ERROR

There are no executables in /OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxIA64I64DPOpt/

I get the following error when I use wmake libso

altix1 src/ODE> wmake libso
SOURCE=ODESolvers/ODESolver/ODESolver.C ; icpc -DlinuxIA64 -DDP -wd654,819,1125,1476,1505,1572 -DICC_IA64_PREFETCH -ansi-alias -O3 -ftz -mP3OPT_ecg_swp_control=0x400000 -fno-alias -mtune=itanium2 -fargument-noalias-global -unroll0 -DNoRepository -IlnInclude -I. -I/home/skabilan/OpenFOAM/OpenFOAM-1.4.1/src/OpenFOAM/lnInclude -KPIC -c $SOURCE -o Make/linuxIA64I64DPOpt/ODESolver.o
icpc: error: could not find directory in which g++ resides
make: *** [Make/linuxIA64I64DPOpt/ODESolver.o] Error 1

my g++ resides in /OpenFOAM/linuxIA64/gcc-4.2.1/bin, but i get the following error when i try to execute g++

/OpenFOAM/linuxIA64/gcc-4.2.1/bin/g++: Exec format error. Binary file not executable.

Can any one help with this?

Thanks
Senthil

[schmidt_d]

Senthil,
It looks like you installed a binary version of g++ that was intended for a different architecture. You will have to download the gcc, g++ source and compile on your own machine. OpenFOAM does work on the IA64.
-David

[eugene]

For the Itanium Altix, it is highly advisable to use the Intel compiler and the native MPI. Speedups of up to 2 have been observed over default gcc + OpenMPI configurations.

[gmcgregor]

I am also trying to install OpenFOAM on an altix machine. Some of the problems I faced were:

(1) Building the code somewhere other than my home directory. Along these lines: OpenDX, gcc, etc. are installed on our system under directories such as /usr/local not OpenFOAM. Wmake does not make it easy to adjust the references.

(2) the installation process is not "native compiler friendly", it really wants gcc, g++ etc. For example, elsewhere in these posts there is mention of a command line arg to icpc or icc specifying which version of g++ or gcc it should refer to.

(3) The configure operations insist on leaving critical libraries in directories named 'dummy'. Why?

(4) paraview, cmake, Qt, etc. are a mish-mash of slightly out of date versions, e.g. paraview will not work with the latest Qt so you need to drop back one rev of QT to build paraview which requires cmake which is not the same as wmake which ... you get the picture :-).

(5) FoamX is really baffling. 'nsd' ?! The network gurus are still scratching their heads over this one. Their question,"Why is anyone trying to run yet another name server?" So we punted FoamX straight away.

(6) The dev version is located somewhere as a compressed tar ball but so far I've only been able to get the code using the 'svn' command provided on the source forge page. My experience so far is that the dev version is even harder to build than the released version.

(7) The released version works on our ia64 machine . . . sort of. Some of the tutorials work and some don't. Any suggestions, scripts or details are appreciated :-).

Thanks
George