BUG: Failure of tutorial cases

Standard tutorials supplied with $FOAM_TUTORIALS fail at few points as listed under:

/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop/tutorialsTest/testLoopReport

@andy @Mattijs

It looks as though you cannot run cases with dynamic code/codeStream?

/home/alex2/prashant/OpenFOAM/ThirdParty-dev-OpenCFD/platforms/linux64/gcc-4.6.2/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.2/../../../../include/c++/4.6.2/x86_64-unknown-linux-gnu/bits/os_defines.h:40:22: fatal error: features.h: No such file or directory compilation terminated.

Is your gcc install complete? - can you try with the system compiler? For the same case (potentialFoam/cylinder) I do not see any errors on my local machine

By Andrew Heather on 2015-12-01T15:14:40 (imported from GitLab project)

Strange, but reproducible error in muttley3.

I tried testing same case in muttley1, and it succeed. Both cases are available under:

/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop/tutorialsTest/basic/potentialFoam

Yes, the compilation of gcc is compelte (/home/alex2/prashant/OpenFOAM/ThirdParty-dev-OpenCFD.develop/platforms/linux64/gcc-4.6.2/bin/gcc)

I retested the tutorials on muttley1.

This time all except foamyHexMesh related tests succeed.

/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop/tutorialsTest.07Dec-muttley1/testLoopReport

Status changed to closed

I found the issue for failure in dynamicCode on other nodes of muttley.

Do following in muttley1 and muttley* to see the difference

ls -ltr /usr/include/

There is a features.h file which is missing on other nodes.

Status changed to reopened

So it is the combination of a gcc compiled on a machine with features.h ("This file is a GNU parallel extension to the Standard C++ Library") and one without.

So, does it makes sense to compile on muttley2 or such machine where this features.h is not present?

Would that work on machines with this file? (combination of muttley1 and muttley2 then?)

@Pawan : adding to circulation list

The idea is that the dynamicCode gets compiled on the same machine as you compile the code itself. So as long as the master process is on muttley1 (which includes features.h) it will be the only one that compiles and the others will just do a dlopen without trying to compile.

Status changed to closed

mentioned in commit 13493c886c59442279ac8d3b43e03e763332a556

mentioned in issue #2967 (closed)