Jeff,
I'll take a look when I'm back at work next week. I work with someone on
the Fortran Standards Committee, so if I can find the code, we can probably
figure out how to fix it.
That said, I know just enough Autotools to cause massive damage and fix
a minor bugs. Can you give me a pointer
I filed https://github.com/open-mpi/ompi/issues/9795 to track the issue; let's
followup there.
I tried to tag everyone on this thread; feel free to subscribe to the issue if
I didn't guess your github ID properly.
--
Jeff Squyres
jsquy...@cisco.com
Jeff,
I'm not sure it'll happen. For understandable reasons (for Intel), I think
Intel is not putting too much emphasis on supporting macOS. I guess since I
had a workaround I didn't press them. (Maybe the workaround has performance
issues? I don't know, but I only ever run with macOS on laptops,
Sweet; thanks!
The top-level Fortran test is here:
https://github.com/open-mpi/ompi/blob/master/config/ompi_setup_mpi_fortran.m4
That file invokes a lot of subtests, all of which are named
config/ompi_fortran_*.m4.
People who aren't familiar with the GNU Autotools may make the mistake of
Fair enough.
For the moment, then, we should probably just document the workaround. I'll
add it to README.md for the 4.0.x/4.1.x series and the upcoming 5.0 RST-based
docs.
I wasn't too excited about making a patch for Libtool -- such that the
workaround wouldn't be needed -- because that
Hello,
I have built openmpi-4.1.2 with latest intel oneapi compilers, including
fortran
but I am facing problems at compilation:
mpif90 toto.f90
Undefined symbols for architecture x86_64:
"_ompi_buffer_detach_f08", referenced from:
import-atom in libmpi_usempif08.dylib
ld:
Oh yeah. I know that error. This is due to a long standing issue with Intel
on macOS and Open MPI:
https://github.com/open-mpi/ompi/issues/7615
You need to configure Open MPI with "lt_cv_ld_force_load=no" at the
beginning. (You can see an example at the top of my modulefile here:
Snarky comments from the NAG tech support people aside, if they could be a
little more specific about what non-conformant Fortran code they're referring
to, we'd be happy to work with them to get it fixed.
I'm one of the few people in the Open MPI dev community who has a clue about
Fortran,
The conclusion we came to on that issue was that this was an issue with Intel
ifort. Was anyone able to raise this with Intel ifort tech support?
--
Jeff Squyres
jsquy...@cisco.com
From: users on behalf of Matt Thompson via
users
Sent: Thursday,
