[manredd]

Dear All,

I am trying to build OpenFOAM2.3.0 on Intel Xeon Phi with OpenMPI-1.6.5. The host processor has RHEL6.4.

I had to install and compile the following packages using -mmic flag on the host processor.

zlib
flex
gmp
mpfr

I created cmake using makeCMake for CGAL. I am using (icc, icpc) with "-mmic" flag for the OpenFOAM compilation.

Also I am using ParaView-3.12.0 as recommended by the OpenFOAM installation manual.

Scotch compilation uses 'mpicc' built during OpenMPI compilation. Along with host of other issues, this dependency resolution seems to be quite a tricky issue.

Also, the icc compiler crashes compiling one of the Scotch files.

mpicc -O3 -DCOMMON_FILE_COMPRESS_GZ -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME -Drestrict=__restrict -mmic -DSCOTCH_PTSCOTCH -shared -fPIC -c dgraph_ghst.c -o dgraph_ghst.o
": internal error: ** segmentation violation signal raised **
Access violation or stack overflow. Please contact Support.
compilation aborted for dgraph_fold_comm.c (code 4)
make[2]: *** [dgraph_fold_comm.o] Error 4
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/manumachu/OpenFOAM/ThirdParty-2.3.0/scotch_6.0.0/src/libscotch'
make[1]: *** [ptscotch] Error 2
make[1]: Leaving directory `/home/manumachu/OpenFOAM/ThirdParty-2.3.0/scotch_6.0.0/src/libscotch'
make: *** [ptscotch] Error 2

The icc compiler I am using is the following:

$ icc --version
icc (ICC) 14.0.2 20140120
Copyright (C) 1985-2014 Intel Corporation. All rights reserved.

The location of the icc compiler follows:
/opt/intel/composer_xe_2013_sp1.2.144

Could you please write to me your related experiences and if you have been successfully able to compile and run OpenFOAM?

Please let me know if you need further information.

Thank you for all the help.

Best Regards
Manredd

[wyldckat]

Greetings Manredd and welcome to the forum!

There is already a thread on an almost identical topic, although not specific to OpenFOAM 2.3.0: http://www.cfd-online.com/Forums/ope...-xeon-phi.html

Best regards,
Bruno