Remove a ban of gcc10 in mpi Port group

[barracuda156]

Do we need this in mpi Port group?

        if {${os.major} < 12} {
	            lappend ::mpi.disabled_compilers -gcc9 -gcc10 -gcc11
	        } elseif {$is_mpich} {
	            # mpich: gcc11 subport currently disabled across-the-board
	            lappend ::mpi.disabled_compilers -gcc11
	        }

It took me quite a while to figure out why sundials that built nicely with gcc7 kept failing with gcc10. Turned out that it is banned here. Info is obsolete, gcc10 and mpich-gcc10 build on 10.5.8 and later.

[kencu (Ken)]

gcc10 is not as yet supported in MacPorts on < 10.6 as all the work needed to integrate it (or even get it to build smoothly) has not been done yet. Perhaps someday it might be, if someone like you gets enthusiastic enough and does it !

Until gcc10 is available in MacPorts, eg by doing this:

sudo port -v install gcc10

the ban must stay.

Aside:

Looking at that block, it looks like gcc9, 10, and 11 are banned on os.major < 12.

If that is true and I'm reading that correctly, note that all gcc compilers build on os.major 10 and 11 for a year or so now, so that might be out of date.

[barracuda156]

Replying to kencu:

gcc10 is not as yet supported in MacPorts on < 10.6 as all the work needed to integrate it (or even get it to build smoothly) has not been done yet. Perhaps someday it might be, if someone like you gets enthusiastic enough and does it !

Until gcc10 is available in MacPorts, eg by doing this:

sudo port -v install gcc10

That’s what I tried obviously and it failed. In particular, sundials fails to configure complaining about incompatible fortran. The problem is nowhere obvious since I have mpich-gcc10 built, gcc10 with gfortran working, yet configure complains. Eventually I began googling the specific error, and that led me to mpi port group file. Bingo: the error has been caused precisely by it.

the ban must stay.

Aside:

Looking at that block, it looks like gcc9, 10, and 11 are banned on os.major < 12.

If that is true and I'm reading that correctly, note that all gcc compilers build on os.major 10 and 11 for a year or so now, so that might be out of date.

It’s up to you to decide, of course, but it seems we agree that at least Darwin10 upwards should not be excluded? (I don’t see any positive utility in this ban tbh. If compiler doesn’t work obviously one cannot build mpich on its base, so banning is redundant. On the other hand if someone fixes compiler then this ban causes unasked error which may not be easy to trace.)

[kencu (Ken)]

I don't want to complicate the discussion overly:

gcc10 is not available in MacPorts on < 10.6.

[kencu (Ken)]

A separate issue is that the mpi portgroup may or may not need to update what it thinks is supported on 10.6 and 10.7, as it looks like that might be out of date.

[barracuda156]

Replying to kencu:

A separate issue is that the mpi portgroup may or may not need to update what it thinks is supported on 10.6 and 10.7, as it looks like that might be out of date.

You are right, and I in fact meant this (this assumption of mpi portgroup caused an error that I referred to).

[Christopher Nielsen <mascguy@…>]

In 55d247a936ccc0212d27cb2352ab1e002ad3705c/macports-ports (master):

openmpi/mpich: gcc 9-11: enable for 10.6 and 10.7

• Once builds validated, will also be enabled for MPI-dependent ports
• CC: @eborisch

See: #64827

[Christopher Nielsen <mascguy@…>]

In 81bf0cdfa6471355989104734c483d0c50d4626f/macports-ports (master):

mpi pg: enable gcc 9-11 for 10.6 and 10.7

• CC: @eborisch

Fixes: #64827