From: "H. J. Lu" <hjl@lucon.org>
To: anemet@lnxw.com
Cc: gcc@gcc.gnu.org
Subject: Mainline is broken
Date: Thu, 11 Nov 2004 01:24:00 -0000 [thread overview]
Message-ID: <20041111003131.GA30416@lucon.org> (raw)
Mainline is broken by
http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00854.html
I got
stage1/xgcc -Bstage1/ -B/usr/gcc-4.0/ia64-unknown-linux-gnu/bin/ -c
-DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-Wno-variadic-macros -Wold-style-definition -Werror -Werror
-DHAVE_CONFIG_H -I. -Icp -I/net/gnu/export/gnu/src/gcc/gcc/gcc
-I/net/gnu/export/gnu/src/gcc/gcc/gcc/cp
-I/net/gnu/export/gnu/src/gcc/gcc/gcc/../include
-I/net/gnu/export/gnu/src/gcc/gcc/gcc/../libcpp/include
/net/gnu/export/gnu/src/gcc/gcc/gcc/cp/typeck.c -o cp/typeck.o
cc1: warnings being treated as errors
/net/gnu/export/gnu/src/gcc/gcc/gcc/cp/typeck.c: In function
'cxx_mark_addressable':
/net/gnu/export/gnu/src/gcc/gcc/gcc/cp/typeck.c:4345: warning: suggest
explicit braces to avoid ambiguous 'else'
make[4]: *** [cp/typeck.o] Error 1
H.J.
next reply other threads:[~2004-11-11 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 1:24 H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-04 16:00 H. J. Lu
2004-09-04 16:06 ` Andreas Schwab
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=20041111003131.GA30416@lucon.org \
--to=hjl@lucon.org \
--cc=anemet@lnxw.com \
--cc=gcc@gcc.gnu.org \
/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).