OpenBLAS binary packages

Chris Jones jonesc at
Wed May 15 08:44:46 UTC 2019

On 15/05/2019 9:35 am, Artur Szostak wrote:
>> Its not possible to get binary installs for OpenBLAS due to license
>> conflicts between it and one of its deps, openssl IIRC. Because of this
>> the buildbots flag the builds as non-distributable.
> OK. But again. If I am trying to get the thing installed from a local repository of my own prebuilt binaries, why does that not work? How is the buildbot involved in that case?

Without more details its hard to comment... Run with 'port -d' to see 
debug messages to see what is actually happening internally.

However, as Joshua has reminded me OpenBLAS internally uses various 
instructions sets, AVX, AVX2 etc. These are not universally available, 
so in order to get the best build for *your* machine it forces the build 
to be run from source each time, so it can determine what your machine 
supports. This is perhaps what is affecting you with your local repo....


>>> I am trying to understand why I am not able to get the OpenBLAS port to install exclusively from binary packages, i.e. using something like:
>>>     sudo port -b install OpenBLAS
>>> Even if I prepare a local repository with the prebuilt binary packages it indicates that it is not able to find any binary package and the above
>>> command fails. I have no such problem with other ports.
>>> I had a quick look to see if there is something in the Portfile itself that forces compilation from source but did not find anything obvious.
>>> Is there such a mechanism? what is it? and can this be disabled / overridden?

More information about the macports-users mailing list