[MacPorts] #63031: mpich-default @3.4.1_3: seems to be disabled on Leopard -- but installs easily

[MacPorts]

#63031: mpich-default @3.4.1_3: seems to be disabled on Leopard -- but installs
easily
---------------------------+---------------------
  Reporter:  kencu         |      Owner:  mascguy
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:  wontfix       |   Keywords:
      Port:  mpich-defaul  |
---------------------------+---------------------

Comment (by eborisch):

 Ken, please be done with your slights. We get it. We're all volunteers
 here, and having someone complain about it in ''every single post'' gets a
 bit old.

 The background is that once upon a time there was a desire to be able to
 test how the different compilers would ''compile the mpich library
 itself'' (for performance / correctness testing), in addition to then
 using the matching compilers (via the generated wrappers and libraries) to
 then compile "user" MPI code.

 Once upon a time, building the library with the compiler you want to use
 for the "user" code was the recommended (by upstream) process to avoid
 unexpected / unsupported errors or configurations. I don't think that is
 still explicitly the case, but there is still a
 [https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Do_I_have_to_configure.2Fmake.2Finstall_MPICH_each_time_for_each_compiler_I_use.3F
 laundry list of things] that need to line up between the library compiler
 and the "user" compiler for things to work right.

 We can certainly have the discussion again if it is time to say "things
 generally work, there is only mpich-default" and move on. I've also
 considered re-doing the compiler-flavored-subports to just generate new
 wrapper scripts, but all use the mpich-default libraries. I have not had
 the time to look at those, and I don't have a schedule for when I will.

 In the interim, Christopher has been doing a lot of work to merge (as much
 as possible) the mpich and openmpi ports such that they stay lined up more
 consistently. I'm sorry something has broken (potentially during this
 process; not really sure) but please be patient and supportive — and be
 done with the caustic comments peppered into your responses. Please add a
 kens-mpich port and start moving ports over to that if you have a better
 solution; indeed if you have a better solution that makes enough people
 happy, it will win; the joy of open source projects!

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