[MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default

[MacPorts]

#66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle
mpich-gcc* but wants mpich-default
---------------------------+-------------------------------------------
  Reporter:  barracuda156  |      Owner:  catap
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.8.0
Resolution:                |   Keywords:  powerpc, leopard, snowleopard
      Port:  scalapack     |
---------------------------+-------------------------------------------

Comment (by kencu):

 Replying to [comment:17 barracuda156]:
 > Replying to [comment:15 kencu]:
 > > Oh, I remember why Chris set it up to always build.
 > >
 > > Iain changes things around sometimes between version bumps, so gcc11.1
 sometimes installed libraries that gcc11.0 did not, for example, and it
 was hard to keep up with that.
 > >
 > > Also, different OS versions and different archs installed different
 libraries.
 > >
 > > So rather than try to keep track of all that nonsense, the portfile
 just looks at the dylibs and installs what is missing. Sometimes that is
 nothing, sometimes that is not nothing.
 >
 > Well, you perhaps remember what Iaian said in that regard: it should not
 be necessary at all.

 It is needed though, as it caused build failures othewise when libraries
 could not be found.

 > However, I do not want to push this change – that may prove too hard,
 and can cause PR to be closed unnecessarily. Also, there is no reason to
 do it in one go. Once the current PR is merged, we can discuss what to do
 with unneeded libgccs.

 check.

 > For gcc12 we only need gcc10-bootstrap and libgcc12, not other versions.

 There will be some work to do, as currently libgcc7 depends on libgcc8
 which depends on ... through to libgcc12. So that has to be sorted out.

 > P. S. By the way, there is one issue which I forgot about: blacklisting
 of gccs in portfile of gcc12 has a weird effect of causing dependency
 cycle. I have no idea why. But I had to remove at least blacklist of
 gcc-4.2, even though it is not used for anything at all, in order for
 gcc10-bootstrap do its work.

 No idea why this would happen.

-- 
Ticket URL: <https://trac.macports.org/ticket/66307#comment:19>
MacPorts <https://www.macports.org/>
Ports system for macOS