edoddridge / aronnax

An idealised isopycnal model that can be run either with n+1/2 layers, or with n layers and variable bathymetry.
http://aronnax.readthedocs.io/en/latest/
MIT License
23 stars 5 forks source link

Possible MPI compilation issue with Ubuntu 20.04 (or new GCC)? #233

Closed nvogtvincent closed 2 years ago

nvogtvincent commented 2 years ago

Hi Ed, not sure if you're still maintaining aronnax but I just wanted to let you know that I've been having issues configuring the Hypre installer on Ubuntu 20.04 with gcc 9.3.0. Specifically, the error message on executing configure is:

checking whether the C compiler works... no configure: error: in '.../aronnax/lib/hypre/src': configure: error: C compiler cannot create executables See 'config.log' for more details

and the problematic error message in config.log seems to be:

configure:4201: $? = 1 configure:4221: checking whether the C compiler works configure:4243: mpicc conftest.c >&5 /usr/bin/ld: cannot find -lmpi collect2: error: ld returned 1 exit status ... configure:4290: error: in '.../aronnax/lib/hypre/src': configure:4292: error: C compiler cannot create executables

It does compile when executing configure --without-MPI though (although the test cases crash). It also works fine (with MPI) on a workstation running Mageia linux and gcc 5.5.0. I don't know enough about c/fortran compilers to work out what the issue is here, nor is this a high priority problem (for me anyway) since I can just run it on the workstation, just wanted to send this as an FYI in case it is a problem with newer versions of gcc and not just me being incompetent (which is more likely).

Config.log: config.log

nvogtvincent commented 2 years ago

Closing this issue because I'm fairly certain it's a problem on my end with Hypre

nvogtvincent commented 2 years ago

Just reopening to post the solution to this problem (on the off-chance anybody else comes across the same issue) - it was indeed a problem on my end, I had a problematic openmpi installation and reinstalling it fixed the problem.

edoddridge commented 2 years ago

Glad you found a solution to this (and that it wasn't a bug!).