You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/04/28 14:51:15 UTC

[jira] [Commented] (TS-562) Custom paths for zlib, openssl, pcre don't work if in non-standard locations without adding --rpath

    [ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982972#comment-13982972 ] 

ASF GitHub Bot commented on TS-562:
-----------------------------------

Github user zwoop commented on the pull request:

    https://github.com/apache/trafficserver/pull/75#issuecomment-41553927
  
    A long time ago, TS-562, we made some changes to (I think?) properly use -rpath with the libtool macros. See commit 449a4e4d83a6665a25371deca36b29ba7f4359df.
    
    I don't know what has happened since then.


> Custom paths for zlib, openssl, pcre don't work if in non-standard locations without adding --rpath
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TS-562
>                 URL: https://issues.apache.org/jira/browse/TS-562
>             Project: Traffic Server
>          Issue Type: Improvement
>    Affects Versions: 2.1.5
>         Environment: Linux
>            Reporter: Marcus Clyne
>            Assignee: Leif Hedstrom
>            Priority: Minor
>             Fix For: 2.1.9
>
>
> When compiling with custom paths for OpenSSL, PCRE, Zlib etc where the paths are in non-standard locations, even if the configure script passes, the libraries may not be linked if their lib path is not in the standard path checked by ld.
> The libraries can be found if extra linker options are passed like -Wl,--rpath=/path/to/lib/dir, but it would make sense to add this automatically on systems that support it if the path is passed to the configure script using --with-openssl=... etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)