Red Hat Bugzilla – Bug 807050
The package openssl-static.x86_64 doesn't work
Last modified: 2012-08-29 13:25:03 EDT
Description of problem:
Red Hat provides a package "openssl-static.x86_64" to staticly link ssl programs, but it doesn't work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a simple program "ssltest.c" that uses openssl:
2. compile and link the program with:
gcc ssltest.c -static `pkg-config openssl --libs --static`
A lot of unresolved symbols to symbols belonging to krb5 library.
Red Hat should provide a static krb5 library and this library should be reported in "pkg-config openssl --libs --static" command.
Similar problem present in F17 (beta)
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in
Red Hat Enterprise Linux 6.4, which is currently under
development. This request will be evaluated for inclusion
in Red Hat Enterprise Linux 6.4.
This seems to be dependent on bug 838782
Well it is dependent only partially - it can be solved independently but of course you'll need static krb5 libraries if you want to create fully statically linked executable which uses openssl.
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
bug 838782 was closed as WONTFIX. Does it make sense to keep this bug opened?
I am not sure - the pkgconfig .pc for openssl is clearly wrong and fixing it would not be bad. But the executables created won't be fully static as krb5 linkage will stay dynamic.
WONTFIXing this bug as well as the fix is of limited use given the missing static krb5 libraries.
If you set this won'tfix, I ask why don't you remove the openssl-static package? It makes no sense to provide a package that never works.
We might remove it in Fedora and future Red Hat Enterprise Linux releases. Removing it in Red Hat Enterprise Linux 6 makes no sense. By the way if you need just the libcrypto, it will be fine as it does not link to krb5 libraries.