On Mon, 19 Mar 2018, Jed Brown wrote: > Satish Balay <[email protected]> writes: > > >> Thanks for the diagnosis. Can we use @rpath/libpetsc.3.08.dylib? Then > >> we wouldn't need to run install_name_tool either. If we want the > >> absolute path written into the dylib, I can do that. > > > > You mean '-install_name ${PREFIXDIR}/lib/libpetsc.3.08.dylib'? Yes - this > > should eliminate the need for install_name_tool in 'make install' [and that > > code can be removed] > > No, I mean -install_name @rpath/libpetsc.3.08.dylib.
mpicc -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress -Wl,-commons,use_dylibs -Wl,-search_paths_first -Wl,-no_compact_unwind -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -Qunused-arguments -fvisibility=hidden -g3 -dynamiclib -install_name -install_name @rpath/libpetsc.3.08.dylib -compatibility_version 3.08 -current_version 3.08.3 -single_module -multiply_defined suppress -undefined dynamic_lookup -o arch-prefix/lib/libpetsc.3.08.3.dylib ... <snip> clang: error: no such file or directory: '@rpath/libpetsc.3.08.dylib' make[2]: *** [arch-prefix/lib/libpetsc.3.08.3.dylib] Error 1 Satish
