Linker problem when building with MPI about opm-core HOT 10 CLOSED

Purely speculation: When MPI is not available, DUNE compiles in "serial" mode; however, when the MPI libraries suddenly "appears", DUNE detects this and wants to enable MPI support but there is some problem which then cascades up.

You'll have to do the REPORTING ISSUES dance from the bottom of the README (it really should be more visible) and post it here.

from opm-core.

When MPI is not available, DUNE compiles in "serial" mode

even worse: by default, it compiles in sequential mode even if MPI is around, unless the --enable-parallel switch is explicitly passed to the configure scripts. fun with libraries...

from opm-core.

it compiles in sequential mode even if MPI is around, unless the --enable-parallel switch is explicitly passed

That kind of goes against my hypothesis. I guess we'll have to wait for the logs to see what's really wrong.

from opm-core.

@laods Is this issue solved by a side-effect of some other change, or is it still relevant?

from opm-core.

I have not tested since I reported this issue, and because my position at Statoil is finished I will not be able to follow it up. I think @alfbr will have to decide whether this issue should be closed or if someone else will take responsibility for it.

from opm-core.

Issue re-assigned to @alfbr for evaluation. Should this be deferred to the 2014.03 release?

from opm-core.

The "on RHEL5 everything builds fine" that @laods mentioned in the first comment is:

-- Finding package MPI using module mode
-- Found MPI_C: /project/res/x86_64_RH_5.2/lib/libmpich.a;/usr/lib64/libpthread.so;/usr/lib64/librt.so 
-- Found MPI_CXX: /project/res/x86_64_RH_5.2/lib/libmpichcxx.a;/project/res/x86_64_RH_5.2/lib/libmpich.a;/usr/lib64/libpthread.so;/usr/lib64/librt.so 

(This is from the log of build 136 of opm-benchmarks; I have added it here as an illustration as that one is not publicly available). Notice that one uses MPICH and one uses OpenMPI. It is unknown (to me) whether MPICH is also installed on RHEL6.

My new hypothesis is now that the MPI libraries don't get added in cmake/Modules/OpmPackage.cmake:284 because the MPI package is "special" (see cmake/Modules/OpmFind.cmake:164).

from opm-core.

I'll defer this to (at least) the next release. If no resolution presents by that time, we'll reevaluate.

from opm-core.

My new hypothesis is now that the MPI libraries don't get added ... because the MPI package is "special"

I no longer believe this, since OpmPackage uses the same find_ routine as everything else, and I've also tested it on a Mac (where I can easily pull away MPI by doing brew unlink openmpi), and I cannot reproduce this problem.

from opm-core.

Since the issue is old, inactive and has not been reproduced by others, I will close it. Reopen if necessary.

from opm-core.