Re: [squid-users] Again: Compile problem with squid-3.1.15

On 14/10/11 21:07, Erich Titl wrote:
> Hi Folks
>
> at 14.10.2011 09:37, Erich Titl wrote:
>> on 13.10.2011 16:46, John Doe wrote:
>>> From: Erich Titl
>>>
>>>> I am still trying to compile 3.1.15. I still get the following
>>>> /usr/lib/libcrypto.a(c_zlib.o): In function `bio_zlib_free':
>>>> (.text+0x4f): undefined reference to `inflateEnd'
>>>
>>> I used your flags and configure on my 32-bits CentOS and 3.1.16 compiled fine...
>>> Maybe make sure you have all the "devel" packages.
>>> Did you check the configure output to see if it detected everything (zlib, ssl...)?
>>
>> I would guess so, anyway compiling with 3.2.0.12 goes without a hitch.
>> Will try with 3.1.16 to see if anything changes.
>
> No changes as expected, 3.1.16 fails compilation just the same.
>
> Is it possible that 3.1 does not play well with openssl 1.0.0x

Very possible.
  They seems to have had no fear of changing the header files
definitions across the 1.0.0* series.

I'm particularly looking now for details like that 'x' in correlation to
particular build errors. So we can use it to target our workarounds as
we encounter problems.

Since you seem to have a working and non-working build. Can you provide
the g++ command line for both 3.2 and 3.1 series build of the broken
file? You provided a 3.1 trace alone earlier. I'm looking for what is
detected differently or ordered differently in the link sequence.

  A diff of the include/autoconf.h file which is generated by
./configure for each of those builds would also be helpful.

And please lets get a bugzilla entry to track all this now.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.15
   Beta testers wanted for 3.2.0.12