You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/12/01 04:26:12 UTC

[jira] Updated: (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:all-tabpanel ]

Leif Hedstrom updated TS-562:
-----------------------------

    Fix Version/s: 2.1.5

> 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
>            Priority: Minor
>             Fix For: 2.1.5
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.