From: Tim Prince <tprince@myrealbox.com>
To: Florian <tslbai@agilolfinger.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc crashes on squid
Date: Sun, 20 Apr 2008 09:50:00 -0000 [thread overview]
Message-ID: <480ACD4F.4050502@myrealbox.com> (raw)
In-Reply-To: <480A8427.800@agilolfinger.de>
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.
prev parent reply other threads:[~2008-04-20 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 6:39 Florian
2008-04-18 9:24 ` David Daney
2008-04-18 18:24 ` Tim Prince
2008-04-20 6:33 ` Florian
2008-04-20 9:50 ` Tim Prince [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480ACD4F.4050502@myrealbox.com \
--to=tprince@myrealbox.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tslbai@agilolfinger.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).