r
>
>
> From: users on behalf of Gilles
> Gouaillardet via users
> Sent: Friday, September 16, 2022 1:41 AM
> To: Open MPI Users
> Cc: Gilles Gouaillardet
> Subject: Re: [OMPI users] ifort and openmpi
>
> Volker,
>
> https://ntq1982.github.io/files/20200621
ers
Cc: Gilles Gouaillardet
Subject: Re: [OMPI users] ifort and openmpi
Volker,
https://ntq1982.github.io/files/20200621.html<https://urldefense.com/v3/__https://ntq1982.github.io/files/20200621.html__;!!OToaGQ!ol_3aOCUHub-qwJg-g0shVNC-LFREtjdhodGzkgca8n2FupNOU7od6bqTquhQ37bxht585bbhx2mAzp_3u22
Volker,
https://ntq1982.github.io/files/20200621.html (mentioned in the ticket)
suggests that patching the generated configure file can do the trick.
We already patch the generated configure file in autogen.pl (if the
patch_autotools_output subroutine), so I guess that could be enhanced
to suppor
Hi all,
This issue here:
https://github.com/open-mpi/ompi/issues/7615
is, unfortunately, still current.
I understand that within OpenMPI there is a sense that this is Intel's problem
but I’m not sure it is. Is it possible to address this in the configure script
in the actual OpenMPI distribu
