[petsc-dev] do we need rpath stuff for directories with only static libraries?

[Jed Brown]

No, we don't need it.

Barry Smith <bsmith at mcs.anl.gov> writes:

>   and how come it is listed twice for the first directory?

Because that doesn't eliminate the redundant stuff like we do for
pkg-config.  BuildSystem is a mess, but I think pkg-config gets it the
way we want.

> $ make getlinklibs
> -Wl,-rpath,/Users/barrysmith/Src/petsc/arch-uni-f2cblaslapack/lib -L/Users/barrysmith/Src/petsc/arch-uni-f2cblaslapack/lib -Wl,-rpath,/Users/barrysmith/Src/petsc/arch-uni-f2cblaslapack/lib -Wl,-rpath,/opt/X11/lib -L/opt/X11/lib -Wl,-rpath,/usr/local/opt/openssl/lib -L/usr/local/opt/openssl/lib -lpetsc -lf2clapack -lf2cblas -lX11 -lssl -lcrypto -ldl
> ~/Src/petsc (maint=) arch-uni-f2cblaslapack
> $ ls arch-uni-f2cblaslapack/
> CMakeCache.txt            bin/                      include/                  obj/
> CMakeFiles/               cmake_install.cmake       initial_cache_file.cmake  
> Makefile                  externalpackages/         lib/                      
> ~/Src/petsc (maint=) arch-uni-f2cblaslapack
> $ ls arch-uni-f2cblaslapack/lib/
> .DIR            libf2cblas.a    libf2clapack.a  libpetsc.a      petsc/          pkgconfig/      
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170430/2b682243/attachment.sig>