OSX: specify the full path to the location of libblis.dylib

[balay]

OSX: specify the full path to the location of libblis.dylib so that it can be found at runtime

Before this change:

Appication gives runtime error [when linked with blis]

dyld: Library not loaded: libblis.3.dylib

balay@kpro lib % otool -L libblis.dylib
libblis.dylib:
        libblis.3.dylib (compatibility version 0.0.0, current version 0.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.0.0)

After this change:

balay@kpro lib % otool -L libblis.dylib
libblis.dylib:
	/Users/balay/petsc/arch-darwin-c-debug/lib/libblis.3.dylib (compatibility version 0.0.0, current version 0.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.0.0)

Note: this build is with:

Executing: ['./configure', '--prefix=/Users/balay/petsc/arch-darwin-c-debug', '--enable-threading=no', 'CC=gcc', 'auto']

[isuruf]

Does the test suite work without installing the library with this change?

[devinamatthews]

@fgvanzee I was afraid this would break moving the library (or not installing it) and setting DYLD_LIBRARY_PATH, but that still works. Looks good to me.

[devinamatthews]

@isuruf test suite works because it uses the static library.

[balay]

I was afraid this would break moving the library (or not installing it) and setting DYLD_LIBRARY_PATH, but that still works. Looks good to me.

@devinamatthews AFAIK for the library to work before copying over - and after copying over - one needs to run install_name_tool separately for each of these steps. And DYLD_LIBRARY_PATH doesn't always work [If I remember correctly - it doesn't propagate to binaries run from scripts]

[devinamatthews]

@balay of course, I just wanted to make sure it worked at least as well as before, which indeed it does.