geerlingguy / top500-benchmark

Automated Top500 benchmark for clusters or single nodes.
MIT License
159 stars 17 forks source link

Failures building MPI with gfortran on 5.4.0-1071-raspi #81-Ubuntu (20.04) #2

Closed brauhausdc closed 9 months ago

brauhausdc commented 1 year ago

Tried to run this on a cluster of pis running Ubuntu 20.04 - it failed trying to build mpi.

Is there a reason not to use the OS provided version of mpich, if available?

Error here:

` failed: [wrk-0002] (item=./configure --with-device=ch3:sock FFLAGS=-fallow-argument-mismatch) => changed=true ansible_loop_var: item cmd:

brauhausdc commented 1 year ago

Also tried with installing gfortran-10 and got similar errors. Seems to work OK on newer versions of Ubuntu on the pi.

geerlingguy commented 1 year ago

@brauhausdc - Honestly I had the same issue on Ubuntu on GitHub Actions, not sure why exactly.

Regarding why I'm compiling mpich, I recall there being some issue with the version that was available for the Pi at the time I initially wrote this playbook for the Turing Pi 2 cluster. That problem may or may not be present anymore, though...

stale[bot] commented 1 year ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

MyloWhylo commented 1 year ago

I was attempting to run this on WSL, and I managed to solve the issue by installing gfortran-10 with apt, then changing line 56 in main.yml to - ./configure --with-device=ch3:sock FFLAGS=-fallow-argument-mismatch FC=gfortran-10. Hopefully this helps someone else out there!

stale[bot] commented 1 year ago

This issue is no longer marked for closure.

github-actions[bot] commented 11 months ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

github-actions[bot] commented 9 months ago

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.