On 2009-03-06 16:26, Jose-Marcio Martins da Cruz wrote:
> Henrik K wrote:
>   
>> On Fri, Mar 06, 2009 at 03:04:04PM +0100, Jose-Marcio Martins da Cruz wrote:
>>     
>>> **************************
>>> checking for gcc bug PR26763-2... ok, bug not present
>>>       
>>     
>>> checking for valid code generation of CLI_ISCONTAINED... configure: 
>>> error: your compiler has a bug that causes clamav bug no. 670, use a 
>>> different compiler, see http://bugs.clamav.net/bugzilla/show_bug.cgi?id=670
>>>       
>>> This a test against a gcc bug. But I'm using cc, and configure knows 
>>> about it, so maybe it shouldn't look for a gcc bug.
>>>       
>> Where does it say it checks a for gcc bug? These two checks have nothing to
>> do with each other.
>>     
>
> Amazing...
>
> At clamav bugzilla web page :
>
> Well, the page above doesn't exists. It was moved to
>       https://wwws.clamav.net/bugzilla/show_bug.cgi?id=670
> which says it's a gcc bug.
>
> But reading the entire page, we see that it happens with SunCC too.
>
> But if I launch configure with --disable-gcc-vcheck, configure doesn't 
> execute this check, all configure continues. So, it seems that configure 
> considers this as a gcc bug and not a generic bug which can be found 
> also in other compilers.
>
> It seems to me that there is some confusion at documentation and/or 
> configure options.

configure --disable-gcc-vcheck appends -O0 to your compiler flags, and
-broken-compiler to your clamav version.
So its normal that all tests pass: they are no longer compiled at -xO3.

All the tests, including those that check for a gcc bug, and the one
that checks for CLI_ISCONTAINED, checks for
code that is miscompiled.
It doesn't matter if its gcc or not, if the code is miscompiled, the
compiler has a bug.
The ones called "checking for gcc bug ..." are called like that because
the testcase comes from the gcc bugzilla, and (in theory) shouldn't affect
any other compiler than gcc 4.0.x and 4.1.0, but you never know.

Best regards,
--Edwin
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to