Bug #19114
radosgw: problem on xenial resolving sonames for libssl.so libcrypto.so
Status:
Duplicate
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The logic I have for resolving sonames at configure time relies on building a dummy program linked against -lssl -lcrypto, then using objdump -p to find out what soname is "NEEDED". This works fine, except on xenial where the compiler/linker defaults to "as-needed".
This was first reported in jewel, so because of deadlines I made a quick fix (automake only) for that. The same fix needs to be made for current versions of ceph which use cmake.
History
#1 Updated by Marcus Watts about 7 years ago
- Status changed from New to Duplicate
Oops. This is a duplicate of 19098. Sorry.