port command hangs under tracemode

[chrstphrchvz (Christopher Chavez)]

Example: configuring openmpi-default @4.0.1_1 under trace mode hangs indefinitely (0% CPU) following this output:

checking if cmpxchg16b_result works... no
checking for assembly architecture... X86_64
checking for builtin atomics... BUILTIN_GCC

*** Fortran compiler
checking whether we are using the GNU Fortran compiler... yes
checking whether /opt/local/bin/gfortran-mp-10 accepts -g... yes
checking whether ln -s works... yes

Interrupting with ctrl-c prints:

^Cchecking if Fortran compiler works...
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_science_openmpi/openmpi-default/work/build" && /opt/local/var/macports/build/_opt_local_var_macports_sources_github.com_macports_macports-ports_science_openmpi/openmpi-default/work/openmpi-4.0.1/configure --prefix=/opt/local --enable-mpi-fortran --enable-mpi-cxx FFLAGS='' F77='' --bindir=/opt/local/libexec/openmpi-mp --libdir=/opt/local/lib/openmpi-mp --sysconfdir=/opt/local/etc/openmpi-mp --includedir=/opt/local/include/openmpi-mp --datadir=/opt/local/share/openmpi-mp --docdir=/opt/local/share/docdelete --mandir=/opt/local/share/mandelete --with-hwloc=/opt/local
Exit code: 1
Error: Aborted: SIGINT received.

[mascguy (Christopher Nielsen)]

I'll take this. Can someone please assign to me?

[mascguy (Christopher Nielsen)]

Just curious, on which macOS release(s) did you encounter this issue?

[chrstphrchvz (Christopher Chavez)]

I currently observe the issue under macOS 10.15.7 (19H15). The configure script has since slightly reorganized its output, but the problem is still when checking the Fortran compiler. Using Activity Monitor, I see that gfortran-mp-10 is waiting on a process collect2 which is blocking on a read() call.

[mascguy (Christopher Nielsen)]

Given that trace made is inherently intrusive, there is certainly the potential for a situation like this.

I'll take a look, but I'm not sure whether this is fixable. How would you rate this priority-wise?

[chrstphrchvz (Christopher Chavez)]

Not high priority to me personally, but I believe I may have encountered a similar issue with other ports (and neglected to open additional reports). One might wait a long time before realizing it is stuck, though.

[mascguy (Christopher Nielsen)]

If you're also seeing this with other unrelated ports, it's a more general issue... and there's no need for additional tickets. Instead, change the summary and description to reflect that, clear the 'port' field, change the 'component' field to "base," and reassign to macports-tickets@….

[chrstphrchvz (Christopher Chavez)]

I believe R may have been another affected port: #61197