Closed jcapriot closed 10 months ago
I would add that running in a directory such that ../lib/libdmumps.dylib
exists (I just put a symlink to lib
in a directory above my cwd) successfully executes.
I was able to get this to work with a bit of hacking, hopefully the steps I took will help to identify where to fix it.
I first had to use install_name_tool
to change the shared library identification name.
install_name_tool -id "@rpath/libdmumps_seq.dylib" libdmumps_seq.dylib
Then I had to forcefully re-sign the signature for it to run (something apparently only necessary on osx-arm64):
codesign --force -s - libdmumps_seq.dylib
Comparing to the makefile command to create libmumps_common.dylib
it would appear that line 224 needs to be patched to include:
-Wl,$(SONAME),lib$(ARITH)mumps$(PLAT)$(LIBEXT_SHARED)
Solution to issue cannot be found in the documentation.
Issue
I've been attempting to build a package that dynamically links against the sequential library and running into several issues. The first is related to #102, which looks to already have a PR open.
For context, I'm running on an OSX arm processor.
After a temporary workaround of removing that import, successfully compiling and linking together the package, I now run into issues at runtime. It is unable to find the library at runtime. Using
otool -L libdmumps_seq.dylib
(on this installed libraries from conda-forge) reveals the following:It would appear that the
rpath
is not set for the first entry of the library (the other librariessmumps_seq
,cmumps_seq
,zmumps_seq
have this same issue). Howeverlibesmumps.dylib
andlibmumps_common_seq.dylib
do not have this issue.Installed packages
Environment info