On 2015-11-18 20:26, David Mandelberg wrote:
> On 2015-11-13 02:45, Richard Hansen wrote:
>> Linux systems don't have this same problem for some reason. It does
>> not hurt to build the shared libraries on Linux systems, however.
>
> Which Linux systems (distributions and versions) have you tested this
> on? (The commit message is fine, I just want to know before approving
> this change.)
* Ubuntu 14.04: the system version is 1.0.1f (sonames have .1.0.0)
and the RFC3779 version is 1.0.2d (sonames also have .1.0.0)
* Fedora 15: system version is 1.0.0j (sonames have .10) and RFC3779
version is 1.0.1p (sonames have .1.0.0)
When the sonames don't match, the linker issues lots of warnings due to
libmysqlclient dynamically linking against the system version of
OpenSSL. These warnings are not indicative of a new issue. Even if the
sonames match or RPSTIR statically links there are still symbol
collisions; the linker just doesn't warn because it can't tell that
there might be a problem.
The right way to fix the linker warnings is to have only a single copy
of the OpenSSL libraries installed in the system. (In other words,
replace the system's OpenSSL libraries with RFC3779-enabled versions, or
figure out how to do RFC3779 validation without requiring an
RFC3779-enabled OpenSSL.) Matching the sonames of the RFC3779-enabled
libraries to the system libraries suppresses the warnings, which hides
the fact that the loader might choose the wrong library when resolving
symbols.
-Richard
------------------------------------------------------------------------------
_______________________________________________
rpstir-devel mailing list
rpstir-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpstir-devel
