OpenBLAS @0.3.1_0+clang+gcc7+lapack Failed to Build

[nhchan]

I have encountered this error during the execution of "port upgrade outdated". My macOS version is 10.13.6, and my Xcode is version 9.4.1 (9F2000).

Here are the relevant lines in the terminal output:

--->  Computing dependencies for OpenBLAS
--->  Fetching distfiles for OpenBLAS
--->  Attempting to fetch OpenBLAS-0.3.2.tar.gz from https://distfiles.macports.org/OpenBLAS
--->  Verifying checksums for OpenBLAS                                               
--->  Extracting OpenBLAS
--->  Applying patches to OpenBLAS
--->  Configuring OpenBLAS
--->  Building OpenBLAS
Error: Failed to build OpenBLAS: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_OpenBLAS/OpenBLAS/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

I am attaching the main.log file.

Please kindly advise. Thank you!

[NicosPavlov]

This issue appears to be the same as in ticket #56919. Please refer to this ticket for the way to solve it. Marking this one as duplicate.

[michaelld (Michael Dickens)]

Indeed it does.

To @nhchan: What does the following return:

port installed cctools

The reason I ask is that cctools used to default to a +llvm* variant, and mine is still at +llvm39 and works. I've had reports that +llvm40 does not work. Guessing that what cctools really needs is an epoch-bump to get the +xcode variant to take.

[mf2k (Frank Schima)]

Adding the epoch won't help. Upgrading a port retains current variants installed, no matter the defaults. Unless the user uses the --enforce-variants flag.

[nhchan]

To @michaelld, I had the +llvm40 variant of cctools. I just replicated the problem with my other computer with the same +llvm40 variant.

In both cases, running port install cctools +xcode before attempting another port upgrade resolved the issue.

Thanks for the responses!

[michaelld (Michael Dickens)]

@nhchan: Excellent! On my systems, it seems that cctools with variants +xcode, +llvm37, +llvm39, and +llvm50 work. Haven't tried the other variants. Maybe my systems are special ... ;)

@mf2k : OK thanks for clarifying. I thought that bumping the epoch is one way to "reset" a port & its variants to whatever is the new default. Do we not have a way to do this inside a Portfile?

[michaelld (Michael Dickens)]

I see that ​this commit is fixing the variant from +llvm* to +xcode for Xcode 9+ ... which is a start. Maybe good enough? I'll test on my older computers & see ... Not the prettiest way to do it, but if it works ...

[mf2k (Frank Schima)]

Replying to michaelld:

@mf2k : OK thanks for clarifying. I thought that bumping the epoch is one way to "reset" a port & its variants to whatever is the new default. Do we not have a way to do this inside a Portfile?

Not directly. AFAIK, the epoch is just part of the port outdated formula and the only way to "upgrade" to a new version with an alphanumerically lower version number.