[bug-notifications] [libneon27 0004984]: Why neon requires application to be linked with openssl ?

[Mantis Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4984 
====================================================================== 
Reported By:                yann
Assigned To:                dam
====================================================================== 
Project:                    libneon27
Issue ID:                   4984
Category:                   
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2012-07-17 23:00 CEST
Last Modified:              2012-07-18 00:24 CEST
====================================================================== 
Summary:                    Why neon requires application to be linked with
openssl ?
Description: 
Hi,

I recently noticed that cadaver was directly linked against libssl also it
doesn't use any of the functions exported by ssl.

After some research, I tracked down the origin of the dependancy on neon.
Indeed neon-config includes ssl in the list of libs that should be linked
against an application that want to be linked against neon.

$ /opt/csw/bin/neon-config --libs
-m32 -xarch=v8 -L/opt/csw/lib -lintl -L/opt/csw/lib -lneon -lnsl -lsocket
-lz -L/opt/csw/lib -lssl -lcrypto -lsocket -lnsl -ldl -lexpat

My question is: is this really necessary ?

If neon is already linked against libssl, why the application should also
link with openssl ?

Thanks in advance for your answer,

Best regards,

Yann


====================================================================== 

---------------------------------------------------------------------- 
 (0010037) dam (administrator) - 2012-07-18 00:24
 https://www.opencsw.org/mantis/view.php?id=4984#c10037 
---------------------------------------------------------------------- 
I didn't write the pkgconfig files myself, so I guess the neon guys
hopefully do it right. The reason I know is that if libfoo has a global
variable and app links to libfoo and libbar which also links to libfoo they
use two separate copies of the global variable instead of a shared one. I
ran into this for the perl backend for OpenLDAP where the perl modules were
not linked directly to libperl.so resulting in strange behaviour.
Apart from that I have no idea how to check this. Ask upstream?