Re: gcc crashes on squid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Florian wrote:

Comodo has discontinued trustix.
So you can't expect the gcc project to support a branch they had no control over.

You might try to build that particular source file without
optimization, while waiting for action on a bug report.
How can i buid it "without optimization"?
I recall you showing the error occured at -O2.  How about -O0 ?

I built a new gcc (4.3.0) from the gnu-sources and have nearly the same
problem:

if /usr/local/gcc430/bin/c++ -DHAVE_CONFIG_H -I. -I. -I../include
-I../include -             I../include    -Werror -Wall -Wpointer-arith
-Wwrite-strings -Wcomments  -g -O2              -MT IPAddress.o -MD -MP
-MF ".deps/IPAddress.Tpo" -c -o IPAddress.o IPAddress.cc             ; \
        then mv -f ".deps/IPAddress.Tpo" ".deps/IPAddress.Po"; else rm
-f ".deps             /IPAddress.Tpo"; exit 1; fi
cc1plus: warnings being treated as errors
IPAddress.cc: In member function 'void
IPAddress::GetAddrInfo(addrinfo*&, int) c             onst':
IPAddress.cc:837: error: suggest parentheses around && within ||

You have -Werror set. If you don't want to heed the advice, you can turn off -Werror to allow things to proceed. This hardly qualifies as "nearly the same problem," although it is a recurring annoyance. In fact, you can easily find PRs about the excessive issuance of this new warning. However, you're asking for it when you set -Wall -Werror ... together.

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux