You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Marcus Clyne (JIRA)" <ji...@apache.org> on 2010/11/25 16:45:13 UTC
[jira] Created: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
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: Bug
Affects Versions: 2.1.5
Environment: Linux
Reporter: Marcus Clyne
Priority: Minor
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.
[jira] [Assigned] (TS-562) Custom paths for zlib, openssl, pcre
don't work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom reassigned TS-562:
--------------------------------
Assignee: Leif Hedstrom (was: Igor Brezac)
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-562) Custom paths for zlib, openssl, pcre
don't work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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: (was: 2.1.8)
2.1.9
Moving these out for v2.1.9 for now.
> 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: Igor Brezac
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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: (was: 2.1.5)
2.1.6
> 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.6
>
>
> 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.
[jira] [Assigned] (TS-562) Custom paths for zlib, openssl, pcre
don't work if in non-standard locations without adding --rpath
Posted by "Eric Connell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Connell reassigned TS-562:
-------------------------------
Assignee: Igor Brezac
This one appears to be right up your alley
> 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: Igor Brezac
> Priority: Minor
> Fix For: 2.1.8
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (TS-562) Custom paths for zlib, openssl, pcre
don't work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom reassigned TS-562:
--------------------------------
Assignee: Leif Hedstrom
> 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.6
>
>
> 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.
[jira] [Resolved] (TS-562) Custom paths for zlib, openssl, pcre
don't work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-562.
------------------------------
Resolution: Fixed
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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: (was: 2.1.7)
2.1.8
> 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.8
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
Posted by "Marcus Clyne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Clyne updated TS-562:
----------------------------
Issue Type: Improvement (was: Bug)
> 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
>
> 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.
[jira] Updated: (TS-562) Custom paths for zlib, openssl, pcre don't
work if in non-standard locations without adding --rpath
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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: (was: 2.1.6)
2.1.7
Assignee: (was: Leif Hedstrom)
> 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.7
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira