py-scipy: seems to opportunistically link against openblas

[petrrr]

I was upgrading openblas earlier and realized that deactivating @0.2.12 broke my py??-scipy ports. So it looks like py-scipy opportunistically links against OpenBLAS.

--->  Activating OpenBLAS @0.2.13_1+gcc48
x ./
x ./+COMMENT
x ./+CONTENTS
x ./+DESC
x ./+PORTFILE
x ./+STATE
x ./opt/
x ./opt/local/
x ./opt/local/include/
x ./opt/local/lib/
x ./opt/local/lib/libopenblas-r0.2.13.a
x ./opt/local/lib/libopenblas-r0.2.13.dylib
x ./opt/local/lib/libopenblas.a
x ./opt/local/lib/libopenblas.dylib
x ./opt/local/include/cblas_openblas.h
x ./opt/local/include/f77blas.h
x ./opt/local/include/openblas_config.h
--->  Cleaning OpenBLAS
--->  Removing work directory for OpenBLAS
--->  Updating database of binaries
--->  Scanning binaries for linking errors
Could not open /opt/local/lib/libXss.1.dylib: Error opening or reading file (referenced from /opt/local/bin/mplayer)
Could not open /opt/local/lib/libopenblas-r0.2.12.dylib: Error opening or reading file (referenced from /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scipy/cluster/_vq.so)
--->  Found 49 broken file(s), matching files to ports   
--->  Found 3 broken port(s), determining rebuild order
--->  Rebuilding in order
     py27-scipy @0.15.1 +gcc48
     py34-scipy @0.15.1 +gcc48
     MPlayer @1.1 

[seanfarley (Sean Farley)]

Well, that's unfortunate.

[petrrr]

Please note that py-numpy seems to show this opportunistic linking behavior as well. See ticket: #45926.

[michaelld (Michael Dickens)]

Should be fixed in r139271. I'll check out the same basic for for the numpy issue. Might also have to add variant checking for +openblas, similar to that for +atlas.