Hi Jose,

the patch you mentioned does not solve the problem (i tried it):

$ otool -D libslepc.dylib
libslepc.dylib:
/private/var/folders/5k/sqpp24tx3ylds4fgm13pfht00000gn/T/davydden/spack-stage/spack-stage-jqcVVv/slepc-3.7.1/installed-arch-darwin-c-opt/lib/libslepc.3.7.dylib

Kind regards,
Denis 

> On 10 Jul 2016, at 18:47, Jose E. Roman <[email protected]> wrote:
> 
> I think this is already fixed in this commit:
> https://bitbucket.org/slepc/slepc/commits/7489a3f3d569e2fbf5513ac9dcd769017d9f7eb7
> Version 7.3.2 containing this patch will be released in a week or so.
> Thanks for reporting this.
> Jose
> 
> 
>> El 10 jul 2016, a las 18:36, Denis Davydov <[email protected]> escribió:
>> 
>> Dear developers,
>> 
>> Slepc 3.6.3 used to produce the following result of install names:
>> 
>> $ otool -lv libslepc.dylib | grep slepc
>> libslepc.dylib:
>>       name 
>> /Users/davydden/spack/opt/spack/darwin-elcapitan-x86_64/clang-7.3.0-apple/slepc-3.6.3-b35zhzknp4lrt5r2iksagql2jkya2vfl/lib/libslepc.3.6.3.dylib
>>  (offset 24)
>>       path 
>> /Users/davydden/spack/opt/spack/darwin-elcapitan-x86_64/clang-7.3.0-apple/slepc-3.6.3-b35zhzknp4lrt5r2iksagql2jkya2vfl/lib
>>  (offset 12)
>>       path 
>> /Users/davydden/spack/opt/spack/darwin-elcapitan-x86_64/clang-7.3.0-apple/slepc-3.6.3-b35zhzknp4lrt5r2iksagql2jkya2vfl/lib64
>>  (offset 12)
>> 
>> same for libslepc.3.6.dylib and libslepc.3.6.3.dylib
>> 
>> 
>> Since [3.7.1] the installed libraries have
>> 
>> $ otool -lv libslepc.dylib | grep slepc
>> libslepc.dylib:
>>       name 
>> /private/var/folders/5k/sqpp24tx3ylds4fgm13pfht00000gn/T/davydden/spack-stage/spack-stage-JwBNAx/slepc-3.7.1/installed-arch-darwin-c-opt/lib/libslepc.3.7.dylib
>>  (offset 24)
>>       path 
>> /Users/davydden/spack/opt/spack/darwin-elcapitan-x86_64/clang-7.3.0-apple/slepc-3.7.1-gimrzhb4mozeus3i2hdmrtjp3tha5pgr/lib
>>  (offset 12)
>>       path 
>> /Users/davydden/spack/opt/spack/darwin-elcapitan-x86_64/clang-7.3.0-apple/slepc-3.7.1-gimrzhb4mozeus3i2hdmrtjp3tha5pgr/lib64
>>  (offset 12)
>> 
>> 
>> That is, the “name” is wrong as it corresponds to the path in the temporary 
>> build folder.
>> 
>> Kind regards,
>> Denis 
>> 
> 

Reply via email to