Re: [squid-users] problem compiling squid 3.2.15 with libecap 0.0.3 and squid-ecap-gzip-1.3.0

On 02/11/2012 05:43 PM, Amos Jeffries wrote:
> On 12/02/2012 11:14 a.m., gewehre_at_gmx.net wrote:
>> I had no problem with the combo of Squid 3.1.1x + libecap 0.0.3 +
>> squid-ecap-gzip-1.3.0. Now that squid 3.2.15 finally compiles on Mac
>> OS X 10.4.11, I
>
> Note for future readers: 3.2.15 has not yet been released. It might be
> one day. The current release is 3.2.0.15.
>
>> tried it with libecap 0.0.3 + squid-ecap-gzip-1.3.0, only to run into
>> the following issue:
>>
>> /bin/sh ../../../libtool --tag=CXX --mode=compile g++
>> -DHAVE_CONFIG_H -I../../.. -I../../../include -I../../../lib
>> -I../../../src -I../../../include -I/usr/include -I/usr/include
>> -I../../../libltdl -I/usr/include -I/usr/include
>> -I/usr/local/include -g -O2 -c -o libsquid_ecap_la-Host.lo `test -f
>> 'Host.cc' || echo './'`Host.cc
>> libtool: compile: g++ -DHAVE_CONFIG_H -I../../.. -I../../../include
>> -I../../../lib -I../../../src -I../../../include -I/usr/include
>> -I/usr/include -I../../../libltdl -I/usr/include -I/usr/include
>> -I/usr/local/include -g -O2 -c Host.cc -fno-common -DPIC -o
>> .libs/libsquid_ecap_la-Host.o
>> ../../../src/adaptation/ecap/MessageRep.h:44: error:
>> 'libecap::NamedValueVisitor' has not been declared
>> Host.cc: In constructor 'Adaptation::Ecap::Host::Host()':
>> Host.cc:34: error: 'headerTransferEncoding' is not a member of 'libecap'
>> make[4]: *** [libsquid_ecap_la-Host.lo] Error 1
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all-recursive] Error 1
>> make[1]: *** [all] Error 2
>> make: *** [all-recursive] Error 1
>>
>>
>> I've attempted substituting in libecap 0.1.0 or 0.2.0, but neither
>> compiles with squid-ecap-gzip-1.3.0, so it's a non-starter there.
>
> squid-ecap-gzip seems not to be relevant. This is Squid not being
> provided with symbol definitions by your libecap development version.

Squid v3.2 supports libecap v0.2.0 only. You canot build Squid v3.2 with
libecap v0.0.3. I am actually surprised your built went that far, but it
could be because libecap v0.0.3 did not even provide library version
information.

If your eCAP adapter is not compatible with libecap v0.2.0, you should
contact the adapter developer and ask them to upgrade their adapter (to
the latest eCAP library version).

HTH,

Alex.
Received on Mon Feb 13 2012 - 19:55:22 MST