OpenFOAM-1.6 on Suse10
 

Hi Foamers,
I have installed OF-1.6 64 bit version on Suse 10. The foamInstallationTest is ok, my precompiled solvers like icoFoam works fine, but when I compile say MRFSimpleFoam, I get the following error

g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3 -DNoRepository -ftemplate-depth-40 -I/software/OpenFOAM/OpenFOAM-1.6/src/turbulenceModels -I/software/OpenFOAM/OpenFOAM-1.6/src/turbulenceModels/incompressible/RAS/RASModel -I/software/OpenFOAM/OpenFOAM-1.6/src/transportModels -I/software/OpenFOAM/OpenFOAM-1.6/src/transportModels/incompressible/singlePhaseTransportModel -I/software/OpenFOAM/OpenFOAM-1.6/src/finiteVolume/lnInclude -IlnInclude -I. -I/software/OpenFOAM/OpenFOAM-1.6/src/OpenFOAM/lnInclude -I/software/OpenFOAM/OpenFOAM-1.6/src/OSspecific/POSIX/lnInclude -fPIC Make/linux64GccDPOpt/MRFSimpleFoam.o -L/software/OpenFOAM/OpenFOAM-1.6/lib/linux64GccDPOpt \
-lincompressibleRASModels -lincompressibleTransportModels -lfiniteVolume -lOpenFOAM -liberty -ldl -lm -o /home/u530655/OpenFOAM/u530655-1.6/applications/bin/linux64GccDPOpt/MRFSimpleFoam
/software/OpenFOAM/OpenFOAM-1.6/lib/linux64GccDPOpt/libincompressibleRASModels.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status

I have tried both installation in alternative locations and default location, both the give the same error. Any suggestion will be of great help. Thanks in advance.

As far as I remember, SuSE 10.2 (released Dec 2006) was the lowest version where the system linker worked properly with the newer gcc versions (eg, those used by OpenFOAM-1.5 and OpenFOAM-1.6).
I'm afraid that the easiest solution is updating your system.

I have found exactly this problem with our 1.6 installation on our Cluster that uses SLES 10. The only way arround this is to compile OpenFOAM on the machine rather than use the binary distributions. I have been told that this is essentially a bug in SLES 10. We have not found the same problem on our Redhat system and I still do not understand why there was no problem with 1.5 and now there is with 1.6.

Regards,
Simon