Re: Problems compiling squid 3.3.8

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Mon, 09 Sep 2013 12:15:54 +1200

On 4/09/2013 3:42 a.m., Alex Rousskov wrote:
> On 09/02/2013 09:01 AM, Christian wrote:
>>
>> Am 02.09.2013 06:29, schrieb Amos Jeffries:
>>> On 2/09/2013 7:32 a.m., Alex Rousskov wrote:
>>>> On 09/01/2013 07:04 AM, Christian wrote:
>>>>> [ 229s] libtool: compile: g++ -DHAVE_CONFIG_H -I../.. -I../../include
>>>>> -I../../lib -I../../src -I../../include -Wall -Wpointer-arith
>>>>> -Wwrite-strings -Wcomments -Werror -pipe -D_REENTRANT -m64
>>>>> -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
>>>>> -funwind-tables -fasynchronous-unwind-tables -fPIC -DOPENSSL_LOAD_CONF
>>>>> -std=c++0x -MT InfoAction.lo -MD -MP -MF .deps/InfoAction.Tpo -c
>>>>> InfoAction.cc -fPIE -o InfoAction.o >/dev/null 2>&1
>>>>> [ 230s] cc1plus: warnings being treated as errors
>>>>> [ 230s] Inquirer.cc: In member function 'virtual void
>>>>> Mgr::Inquirer::start()':
>>>>> [ 230s] Inquirer.cc:90: error: 'auto_ptr' is deprecated (declared at
>>>>> /usr/include/c++/4.3/backward/auto_ptr.h:91)
>>>>> Can somebody help, please?
>>>> I suggest filing a bug report (if there is not one already) and then
>>>> building Squid without -Werror in CXXFLAGS.
>>> The bug here is in the version mismatch between GCC libraries/headers vs
>>> compiler unfortunately.
>>>
>>> Somebody appears to have added (has RHEL back-porting struck again?)
>>> that deprecation warning into GCC headers a version or so before the
>>> compiler support for C++11 unique_ptr. So our code tests for which
>>> built-in pointer type is available select auto_ptr and hit that
>>> nastiness. Not using it will crash randomly, using it will not build
>>> with -Werror.
>>>
>>> An upgrade of the compiler is highly recommended. Second best choice is
>>> the --disable-strict-error-checking configure option which disables
>>> -Werror cleanly and make sure -Werror is not also in any custom flags.
>>>
>>> Amos
>> Hi Amos,
>>
>> so if I understand you correctly I should use
>> configure --disable-strict-error-checking
>
> IMO, you should file a bug report with Squid bugzilla (quoting Amos
> explanation above or linking to this thread) and then either use
> --disable-strict-error-checking or upgrade your GCC (sorry, I do not
> know which version).
>
> Alex.
>

The ony bug in Squid is that we do not exactly mention the compiler
minimum version requirements anywhere clearly.
It is pretty much just a flexible idea in my head right now as to what
compilers people or Jenkins testing are finding problems with vs squid
vesions.

Amos
Received on Mon Sep 09 2013 - 00:16:01 MDT

This archive was generated by hypermail 2.2.0 : Mon Sep 09 2013 - 12:00:12 MDT