On Nov 9, 2007, at 2:08 AM, Ralf S. Engelschall wrote:
>>
>> What's the best way to get rid of these leaks? I understand perfectly
>> why a neon library cannot eliminate the leaks, see the comments in
>> ne_sock_init.
>
> Can't RPM just call OpenSSL's ERR_free_strings() explicitly itself in
> case it knows it is using NEON (we provide "WITH_NEON") and NEON is
> using SSL (<ne_utils.h> provides "NE_FEATURE_SSL")?
>

But doesn't that force rpm to also be explicitly (rather than  
implicitly) linked with openssl?

I can't justify linking openssl to get rid of a valgrind message ...

73 de Jeff