On May 22, 2013, at 03:39 , Eliezer Croitoru wrote:
> On 5/22/2013 10:20 AM, Alex Domoradov wrote:
>> I think the easiest way to find out with which version of openssl was
>> link squid is to use ldd
>>
>> # ldd /usr/sbin/squid | grep ssl
>> libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007ff8b13d6000)
> From mine.
> # ldd /usr/sbin/squid |grep ssl
> libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f2a8dbf1000)
> it's not the same..
>
> So what do we do?
> I can send the openssl RPM I am using to someone if he needs it.
From mine:
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f08f8eb2000)
I think that last number is simply a memory address, so it could be located
at a variety of different places depending on how squid was linked. Using
different options (such as, I'm not using kerberos) would affect that.
The important thing is the major version of the library for ABI
compatibility. We're all the same on that, they're all just variants of 1.0.0.
And, the issue in question isn't the library anyway. Linking isn't a problem,
it's compilation. The headers are what would need to change, or perhaps the
compiler or compilation options.
I also got a report back from my systems team that --enable-ssl works fine on
our systems, but --enable-ssl-crtd causes the compilation failure I'm seeing.
You used both of those, Eliezer?
- Chris
