CFD Online Discussion Forums - [OpenFOAM.org] OpenFOAM 4.0 compilation fails with latest Intel compiler

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- OpenFOAM Installation (https://www.cfd-online.com/Forums/openfoam-installation/)

- - [OpenFOAM.org] OpenFOAM 4.0 compilation fails with latest Intel compiler (https://www.cfd-online.com/Forums/openfoam-installation/177696-openfoam-4-0-compilation-fails-latest-intel-compiler.html)

OpenFOAM 4.0 compilation fails with latest Intel compiler

Hi, when trying to build OpenFOAM 4.0 with the latest release of the Intel compilers (2017.0.020), I keep getting the following error:

Code:

OpenFOAM/OpenFOAM-4.0/src/OpenFOAM/lnInclude/MatrixSpaceI.H(492): error: no instance of overloaded function "Foam::MatrixSpace<Form, Cmpt, Mrows, Ncols>::Block<SubTensor, BRowStart, BColStart>::operator=" matches the specified type

  operator=

  ^

preceded by these warnings:

Code:

OpenFOAM/OpenFOAM-4.0/src/OpenFOAM/lnInclude/MatrixSpaceI.H(494): warning #2357: "Foam::MatrixSpace<Form2, Cmpt, SubTensor::mRows, SubTensor::nCols>" cannot be specified in a template member definition -- "Foam::MatrixSpace<Form, Cmpt, Mrows, Ncols>" assumed instead

      const MatrixSpace<Form2, Cmpt, SubTensor::mRows, SubTensor::nCols>& matrix

            ^

This didn't seem to happen with the previous Intel version (2016).
So, is this a bug in the OpenFOAM source code, or maybe there is a flag I can use for the compiler so that it behaves like the old version and does not throw an error in this case?
Any help would be appreciated.

Quick answer: Please report this on the OpenFOAM Foundation bug tracker: http://bugs.openfoam.org - they are keeping track of Intel's compiler support.

Bruno,

I had the same issue with Intel-2017. I didn't see an open ticket so I submitted one (0002281).

Hi Dan,

Excellent! Paul Edwards stepped in to fill you in on the bug as well!

For a quicker future reference, here is the link for the bug report: http://bugs.openfoam.org/view.php?id=2281
And quoting Paul from his comment there:

Quote:

There was a bug in the Intel compiler front end which has now been fixed. Anything with a timestamp after 20160804 should include the fix. If you cannot get a more recent version then you can apply the patch I have attached.

Best regards,
Bruno