Building libcrypto/libssl without symbolic link

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 22, 2015, at 12:49 PM, Viktor Dukhovni wrote:
> Applications using a non-system library need to record a suitable
> RPATH (often using "$ORIGIN" is a good bet if the application ships
> a copy of the library).  Ideally applications would use the system
> supplied library, otherwise patching becomes rather difficult...

Along similar lines, it would be useful to get RPATH'ing *in* openssl straigthened out

 "openssl 1.0.2 shared build's linking is not consistent - bin and libs linked to different libcrypto.so's"
  https://marc.info/?l=openssl-users&m=142858615805070&w=2



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux