Opened 7 weeks ago

Last modified 7 weeks ago

#60491 new defect

openmpi @4.0.1_1: openmpi-gcc10 - missing subport

Reported by: majoc-at-astro (majoc-at-astro) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: openmpi

Description

The subject says it all, really: openmpi-default has the variant gcc10 present and pre-enabled, but there is no matching subport openmpi-gcc10:

~ % port info openmpi-gcc10         
Error: Port openmpi-gcc10 not found
~ % port info openmpi-default
openmpi-default @4.0.1_1 (science, parallel, net)
Variants:             g95, [+]gcc10, gcc44, gcc45, gcc46, gcc47, gcc48, gcc49,
                      gcc5, gcc6, gcc7, gcc8, gcc9, universal, valgrind
[snip]

My apologies if this sounds like nit-picking. I'll leave it for someone more knowledgeable to check the minimum necessary version of macOS (cf the conditionals round adding the subport openmpi-gcc9).

Change History (2)

comment:1 Changed 7 weeks ago by majoc-at-astro (majoc-at-astro)

Apologies again (my wetware's past its use-by date): This is for macOSsen 10.13--10.15; and our MacPorts builds are done from fresh, twice a week. Please let me know if there's any more details you need.

comment:2 Changed 7 weeks ago by majoc-at-astro (majoc-at-astro)

Today's discoveries:

  • openmpi-gcc10 being found missing causes port select mpi openmpi-gcc10-fortran to fail. (The Warning's there in our build logs, but it's easily overlooked.)
  • Thereafter, port install gnudatalanguage without +openmpi fails to find mpi.h, result Misery.
  • On the offchance. I tried port install openmpi-gcc9, which failed with ptrdiff_t type is not available. This is an early (non-)result; potential links with ticket:59818 may quite possibly include at least one red herring. Logfile available if necessary, and if reproducible in our nightly runs.

Please do let me know if there's anything else I could try. Thanks in advance.

Note: See TracTickets for help on using tickets.