mpich-default: hangs up during configuring

[aehofmann]

Currently attempting to install mpich-default on my Mac in order to ultimately install Quantum Espresso, but the terminal just hangs in the configuring stage, so I don't even have a log file to share.

Running MacOS 10.15.7; XCode 12.4 (build version 12D4e)

$ sudo port -t install mpich-default

gets stuck (as in sitting there for HOURS, dots no longer moving) with 'gfortran-mp-11' in the terminal header:

--->  Configuring mpich-default
      [   •   •   •   •   •   •   •   •   •   •   •   •]

After looking through a bunch of tickets, I confirmed that gfortran-mp-11 is in the opt/local/bin directory. However, all of my mpich-related wrappers are pointing to mpich-gcc10 from a previous install, so I uninstalled all ports and then tried again with

$ sudo port -t install mpich-default -gcc11 +gcc10

but I end up with the same stall-out on mpich-default configuration (this time with gfortran-mp-10 in the header) plus some nice warnings.

--->  Extracting mpich-default
Warning: The following existing file was hidden from the build system by trace mode:
  /private/var/select/sh
--->  Applying patches to mpich-default
Warning: The following existing file was hidden from the build system by trace mode:
  /private/var/select/sh
--->  Configuring mpich-default
      [   •   •   •   •   •   •   •   •   •   •   •   •]

Any suggestions or insight into where I might be going awry would be greatly appreciated.

[jmroot (Joshua Root)]

There should still be a log for what has been completed, under /opt/local/var/macports/logs, and running port logfile mpich-default should show the path to it. Alternatively you could run in debug mode (-d) to show the logged information in the terminal.

Does installing without trace mode make any difference?

[aehofmann]

log file corresponding to installation problem

[aehofmann]

Ack, sorry, I didn't go deep enough into the directory to pull out the main.log file. I've attached it to the ticket. I am using trace mode because I also have Homebrew installed (to work with applications not supported by Macports), and my understanding was that trace mode may be the best way to avoid conflicts between the two. If there's nothing diagnostic in the logfile, then I'll try without -t.

[jmroot (Joshua Root)]

Replying to aehofmann:

I am using trace mode because I also have Homebrew installed (to work with applications not supported by Macports), and my understanding was that trace mode may be the best way to avoid conflicts between the two.

Sure, that makes sense. It would just be nice to rule out the possibility of a bad interaction with the trace mode mechanisms if possible. You could run sudo port configure mpich-default to see if it hangs without trace mode, and then clean afterwards so you don't end up installing anything built that way.

I'll let the maintainers take it from here.

[aehofmann]

Good call. Per your suggestion, I ran $ sudo port configure mpich-default -gcc11 +gcc10

End result:

--->  Computing dependencies for mpich-default
--->  Fetching distfiles for mpich-default
--->  Verifying checksums for mpich-default
--->  Extracting mpich-default
--->  Applying patches to mpich-default
--->  Configuring mpich-default
Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled:
  VALGRIND_DESTROY_MEMPOOL: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  VALGRIND_MEMPOOL_FREE: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  VALGRIND_PRINTF_BACKTRACE: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  VALGRIND_CREATE_BLOCK: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  VALGRIND_MEMPOOL_ALLOC: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  __atomic_load_8: found in mpich-3.4.2/modules/libfabric/config.log
  VALGRIND_CREATE_MEMPOOL: found in mpich-3.4.2/src/mpl/config.log, mpich-3.4.2/src/pm/hydra/mpl/config.log
  exit: found in mpich-3.4.2/modules/json-c/config.log

I don't know enough to know what to make of this output. I will attach the log file from the configuration to this ticket.

[aehofmann]

logfile from running configure without trace mode

[mascguy (Christopher Nielsen)]

The reasoning behind use of Trace mode certainly makes sense. But if you're on a relatively tight deadline, it might be worth installing without Trace enabled. (At least for now, while we troubleshoot this.)