This is very odd ... I dumped DISABLE_io_romio341, and it is *not* set (!)
Anyway, let's follow-up at https://github.com/open-mpi/ompi/issues/11088 Cheers, Gilles On Fri, Nov 18, 2022 at 5:37 PM Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > Let me take a step back... > > Looking at the code, it should work ... except it does not :-( > > > $ configure --enable-mca-no-build=io-romio341 > [...] > checking which components should be disabled... io-romio341 > [...] > +++ Configuring MCA framework io > checking for no configure components in framework io... > checking for m4 configure components in framework io... ompio, romio341 > > --- MCA component io:ompio (m4 configuration macro) > checking for MCA component io:ompio compile mode... static > checking if MCA component io:ompio can compile... yes > > --- MCA component io:romio341 (m4 configuration macro) > checking for MCA component io:romio341 compile mode... static > checking if want ROMIO component... yes > checking if MPI profiling is enabled... yes > > *** Configuring ROMIO distribution > configure: OPAL configuring in 3rd-party/romio341 > > On Fri, Nov 18, 2022 at 5:18 PM Gilles Gouaillardet < > gilles.gouaillar...@gmail.com> wrote: > >> Well, --enable-mca-no-build=io-romio341 works strictly speaking (it does >> not build the io/romio341 component). >> >> That being said, it does not prevent 3rd-party/romio from being built, >> and this is what fails with gcc 4.8 >> >> I will file an issue in order to keep track of that. >> >> >> Cheers, >> >> Gilles >> >> On Fri, Nov 18, 2022 at 9:07 AM Barrett, Brian via devel < >> devel@lists.open-mpi.org> wrote: >> >>> --enable-mca-no-build=io-romio341 should still work. Or just >>> --disable-io-romio. >>> >>> No comment around the RHEL7 part; that's pretty old, but I don't think >>> we've officially said it is too old. Probably something worth filing a >>> ticket for so that we can run to ground before 5.0 release. Oddly, CI >>> continues to pass on RHEL7 in AWS. I'm not sure what we've done to cause >>> that, but also worth investigating. >>> >>> Brian >>> >>> On 11/14/22, 10:32 PM, "devel on behalf of Gilles Gouaillardet via >>> devel" <devel-boun...@lists.open-mpi.org on behalf of >>> devel@lists.open-mpi.org> wrote: >>> >>> CAUTION: This email originated from outside of the organization. Do >>> not click links or open attachments unless you can confirm the sender and >>> know the content is safe. >>> >>> >>> >>> Folks, >>> >>> >>> I tried to build on a RHEL7 like, and it fails at make time because >>> ROMIO requires stdatomic.h >>> >>> (it seems this file is only available from GCC 4.9) >>> >>> >>> Are we supposed to be able to build Open MPI 5 with GCC 4.8 (e.g. >>> stock >>> RHEL7 compiler)? >>> >>> >>> --enable-mca-no-build=io-romio314 cannot help since ROMIO has been >>> moved >>> to 3rd-party >>> >>> is there an other workaround? if not, should be add something like >>> --enable-3rd-party-no-build=romio? >>> >>> >>> Cheers, >>> >>> >>> Gilles >>> >>> On 10/22/2022 6:23 AM, Austen W Lauria via devel wrote: >>> > Open MPI v5.0.0rc9 is now available for testing >>> > athttps://www.open-mpi.org/software/ompi/v5.0/ >>> > <https://www.open-mpi.org/software/ompi/v5.0/>. >>> > >>> > Please test, and send feedback either via the user mailing lists, >>> or >>> > create an issue athttps://github.com/open-mpi/ompi/issues/ >>> > <https://github.com/open-mpi/ompi/issues/> . >>> > >>> > Seehttps://docs.open-mpi.org/en/v5.0.x/news/news-v5.0.x.html >>> > <https://docs.open-mpi.org/en/v5.0.x/news/news-v5.0.x.html> for a >>> list >>> > of changes since rc8. >>> > >>> > Thank you, >>> > v5.0 Release Managers >>> >>> >>>
