On Mon, 19 Mar 2018, Jed Brown wrote:

> Satish Balay <[email protected]> writes:
> 
> > Ok - the issue is coming from the change in jed/gmakefile-paths
> >
> > commit 8e69c5ec7dbec5c4ff0e2255fa41e86223635a8c
> > Author: Jed Brown <[email protected]>
> >
> > Previously we had:
> >
> > /Users/petsc/petsc.next/arch-osx-10.6/bin/mpicc 
> > -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress 
> > -Wl,-commons,use_dylibs -Wl,-search_paths_first -Wl,-no_compact_unwind 
> > -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 arch-osx-10.6/lib/libpetsc.3.08.dylib -compatibility_version 
> > 3.08 -current_version 3.08.3 -single_module -multiply_defined suppress 
> > -undefined dynamic_lookup -o arch-osx-10.6/lib/libpetsc.3.08.3.dylib ...
> 
> I assume the above and below are backwards?

Yeah - sorry.

> 
> > Now we have:
> >
> > /Users/petsc/petsc.master/arch-osx-10.6/bin/mpicc 
> > -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress 
> > -Wl,-commons,use_dylibs -Wl,-search_paths_first -Wl,-no_compact_unwind 
> > -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 
> > /Users/petsc/petsc.master/arch-osx-10.6/lib/libpetsc.3.08.dylib 
> > -compatibility_version 3.08 -current_version 3.08.3 -single_module 
> > -multiply_defined suppress -undefined dynamic_lookup -o 
> > /Users/petsc/petsc.master/arch-osx-10.6/lib/libpetsc.3.08.3.dylib .....
> >
> > '-install_name arch-osx-10.6/lib/libpetsc.3.08.dylib' vs
> > '-install_name 
> > /Users/petsc/petsc.master/arch-osx-10.6/lib/libpetsc.3.08.dylib'
> > is causing this difference.
> 
> 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]

Satish

Reply via email to