mpich-default 4.0.2: Failed to build mpich-default on Macbook Pro osx 10.13.6

[Tom-Bertin]

While trying to install Octave, which is dependant on mpich-default, I get the following error messages:

--->  Building mpich-default
Error: Failed to build mpich-default: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port octave failed

I get the exact same error while installing mpich-default separately. I tried installing several times, did a port clean (octave as well as mpich-default), but nothing worked.

Funny thing is, until yesterday I had Octave and mpich-default installed on my system already for a few months. It worked perfectly. Yesterday I removed all macports packages, and tried to install them again, but now I get these errors.

Am I doing something wrong? Are there other things (packages, configurations, ...) I need to have checked before trying to install mpich-default (or octave)? Or is my system outdated and too old? How do I find out where the problem is situated?

My system is:

• Macbook Pro late 2011;
  
• OS 10.13.6;
  
• macports base version 2.7.2;
  
• Xcode 10.1 (10B61);
  

Things I think are also important mentioning:

• next to macports I also had Homebrew installed. It could be (but I don't remember well) that mpich-default was installed previously via Homebrew, but I removed all Homebrew packages, and removed Homebrew from my system.
• The reason behind removing all macports packages and reinstalling them, and removing Homebrew from my system, was because of an error while building "isl". It turned out this error originated from a very recent update of the isl package; my system turned out to be OK.

Many thanks, and best regards,

[Tom-Bertin]

zipped version of main.log

[mascguy (Christopher Nielsen)]

Based on the log, MacPorts isn't finding an installed version of Xcode.

Do you have a full version of Xcode - and not just the Xcode Command-Line Tools - installed?

:debug:sysinfo macOS 10.13.6 (darwin/17.7.0) arch i386
:debug:sysinfo MacPorts 2.7.2
:debug:sysinfo Xcode none

Also, can you provide the output from xcodebuild -version, along with xcode-select -p?

[mascguy (Christopher Nielsen)]

Eric, I'm wondering if we should allow buildbot binaries to be used for openmpi-default and mpich-default, per our past discussions?

Worst-case, if it causes issues for some macOS/Xcode combinations, we can always revert. But if everything does work properly, users would certainly appreciate not having to build from source!

Thoughts all...?

[mascguy (Christopher Nielsen)]

Tom, in the interim, I'm testing on 10.13 to see if your issue is reproducible. I'll try with both Xcode 9.4.1, as well as 10.1, to cover all bases.

[Tom-Bertin]

Hi,

Thanks for the quick response.

§ xcodebuild -version
Xcode 10.1
Build version 10B61

§ xcode-select -p
/Applications/Xcode.app/Contents/Developer

About Xcode.

Based on the log, MacPorts isn't finding an installed version of Xcode. Do you have a full version of Xcode - and not just the Xcode Command-Line Tools - installed?

I saw this as well, just after I filed this ticket. I did the following:

§ port diagnose
Error: currently installed version of Xcode, none, is not supported by MacPorts.  For your currently installed system, only the following versions of Xcode are supported:  10.1 10.0 9.4.1 9.4 9.3.1 9.3 9.2 9.1 9.0.1 9.0

§ xcode-select -r
§ sudo port diagnose
§ sudo xcode-select --install
Password:
xcode-select: error: command line tools are already installed, use "Software Update" to install updates

After this the commands you asked returned versions numbers and locations. So this seems to be OK now. I don't understand this. I had xcode installed already a while ago.

But, the problem with octave and mpich-default still remains:

§ sudo port install octave
--->  Computing dependencies for octave
The following dependencies will be installed: 
 mpich-default
 sundials
Continue? [Y/n]: y
--->  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-4.0.2/src/mpl/config.log
  VALGRIND_MEMPOOL_FREE: found in mpich-4.0.2/src/mpl/config.log
  VALGRIND_PRINTF_BACKTRACE: found in mpich-4.0.2/src/mpl/config.log
  VALGRIND_CREATE_BLOCK: found in mpich-4.0.2/src/mpl/config.log
  VALGRIND_MEMPOOL_ALLOC: found in mpich-4.0.2/src/mpl/config.log
  __atomic_load_8: found in mpich-4.0.2/modules/libfabric/config.log
  VALGRIND_CREATE_MEMPOOL: found in mpich-4.0.2/src/mpl/config.log
  exit: found in mpich-4.0.2/modules/json-c/config.log
--->  Building mpich-default
Error: Failed to build mpich-default: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port octave failed

[Tom-Bertin]

Oh, and yes, I have the full xcode 10.1 installed on my system.

[mascguy (Christopher Nielsen)]

Given that MacPorts can't identify the Xcode version, you'll want to reinstall the Xcode CLT:

​https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

[mascguy (Christopher Nielsen)]

Replying to mascguy:

Tom, in the interim, I'm testing on 10.13 to see if your issue is reproducible. I'll try with both Xcode 9.4.1, as well as 10.1, to cover all bases.

I'm able to successfully build via both Xcode 9.4.1, as well as 10.1. So reinstall Xcode CLT 10.1, and give it another try.

[Tom-Bertin]

Reinstalling Xcode CLT did the job\\

After reinstalling CLT, 'selfupdate' + 'upgrade outdated' started installing libgcc11 (which took hours!). This was the first time libgcc11 appeared in a list of dependencies or ports that needed updating. After that everything seemed normal again.

Thanks a lot for the great help!

Best regards,

[mascguy (Christopher Nielsen)]

Great, glad the issue is resolved!