public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43729] Mach-O LTO support needed for darwin
Date: Sat, 01 May 2010 15:26:00 -0000 [thread overview]
Message-ID: <20100501152603.20705.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43729-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from dominiq at lps dot ens dot fr 2010-05-01 15:26 -------
Sorry to bother you, but with the patch in comment #19 bootstrap fails at stage
2 with the infamous "all warnings being treated as errors":
...
/opt/gcc/build_w/./prev-gcc/xgcc -B/opt/gcc/build_w/./prev-gcc/
-B/opt/gcc/gcc4.6w/x86_64-apple-darwin10/bin/
-B/opt/gcc/gcc4.6w/x86_64-apple-darwin10/bin/
-B/opt/gcc/gcc4.6w/x86_64-apple-darwin10/lib/ -isystem
/opt/gcc/gcc4.6w/x86_64-apple-darwin10/include -isystem
/opt/gcc/gcc4.6w/x86_64-apple-darwin10/sys-include -c -g -O2 -gtoggle
-DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Werror -Wold-style-definition
-Wc++-compat -fno-common -DHAVE_CONFIG_H -I. -Ilto -I../../work/gcc
-I../../work/gcc/lto -I../../work/gcc/../include
-I../../work/gcc/../libcpp/include -I/opt/sw64/include -I/opt/sw64/include
-I../../work/gcc/../libdecnumber -I../../work/gcc/../libdecnumber/dpd
-I../libdecnumber -I/opt/sw64/include -I/opt/sw64/include -DCLOOG_PPL_BACKEND
-I/opt/sw64/include ../../work/gcc/lto/lto-macho.c -o lto/lto-macho.o
In file included from ../../work/gcc/lto/lto-macho.c:31:0:
../../work/gcc/lto/lto-macho.h:221:33: error: using 'lto_mach_o_data' as both a
typedef and a tag is invalid in C++ [-Werror=c++-compat]
../../work/gcc/lto/lto-macho.h:205:8: note: originally defined here
../../work/gcc/lto/lto-macho.h:255:36: error: using 'lto_mach_o_section' as
both a typedef and a tag is invalid in C++ [-Werror=c++-compat]
../../work/gcc/lto/lto-macho.h:206:8: note: originally defined here
cc1: all warnings being treated as errors
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43729
next prev parent reply other threads:[~2010-05-01 15:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 15:51 [Bug target/43729] New: MachO " howarth at nitro dot med dot uc dot edu
2010-04-12 15:55 ` [Bug target/43729] " steven at gcc dot gnu dot org
2010-04-12 16:00 ` steven at gcc dot gnu dot org
2010-04-12 16:16 ` steven at gcc dot gnu dot org
2010-04-12 17:12 ` howarth at nitro dot med dot uc dot edu
2010-04-12 21:39 ` fang at csl dot cornell dot edu
2010-04-14 22:10 ` [Bug target/43729] Mach-O " steven at gcc dot gnu dot org
2010-04-15 13:49 ` howarth at nitro dot med dot uc dot edu
2010-04-15 14:04 ` stevenb dot gcc at gmail dot com
2010-04-19 7:40 ` steven at gcc dot gnu dot org
2010-04-26 14:49 ` mrs at gcc dot gnu dot org
2010-04-26 16:07 ` stevenb dot gcc at gmail dot com
2010-04-26 18:40 ` davek at gcc dot gnu dot org
2010-04-27 2:35 ` davek at gcc dot gnu dot org
2010-04-27 20:25 ` steven at gcc dot gnu dot org
2010-04-28 12:20 ` dominiq at lps dot ens dot fr
2010-04-28 13:04 ` dominiq at lps dot ens dot fr
2010-04-28 19:50 ` steven at gcc dot gnu dot org
2010-04-29 10:48 ` steven at gcc dot gnu dot org
2010-04-29 11:39 ` steven at gcc dot gnu dot org
2010-04-29 13:20 ` howarth at nitro dot med dot uc dot edu
2010-05-01 14:40 ` steven at gcc dot gnu dot org
2010-05-01 14:43 ` steven at gcc dot gnu dot org
2010-05-01 14:53 ` rguenth at gcc dot gnu dot org
2010-05-01 15:26 ` dominiq at lps dot ens dot fr [this message]
2010-05-01 21:40 ` dominiq at lps dot ens dot fr
2010-05-01 21:51 ` steven at gcc dot gnu dot org
2010-05-01 22:19 ` howarth at nitro dot med dot uc dot edu
2010-05-01 22:31 ` stevenb dot gcc at gmail dot com
2010-05-01 23:22 ` mrs at gcc dot gnu dot org
2010-05-01 23:59 ` howarth at nitro dot med dot uc dot edu
2010-05-02 0:01 ` howarth at nitro dot med dot uc dot edu
2010-05-02 0:07 ` howarth at nitro dot med dot uc dot edu
2010-05-02 0:10 ` howarth at nitro dot med dot uc dot edu
2010-05-02 0:48 ` howarth at nitro dot med dot uc dot edu
2010-05-02 1:24 ` mrs at gcc dot gnu dot org
2010-05-02 13:11 ` howarth at nitro dot med dot uc dot edu
2010-05-02 13:59 ` howarth at nitro dot med dot uc dot edu
2010-05-02 19:16 ` howarth at nitro dot med dot uc dot edu
2010-05-03 21:40 ` mrs at gcc dot gnu dot org
2010-05-03 22:01 ` howarth at nitro dot med dot uc dot edu
2010-05-03 22:15 ` steven at gcc dot gnu dot org
2010-05-03 22:47 ` mrs at gcc dot gnu dot org
2010-05-03 23:41 ` howarth at nitro dot med dot uc dot edu
2010-05-04 8:22 ` mrs at gcc dot gnu dot org
2010-05-07 22:23 ` steven at gcc dot gnu dot org
2010-05-08 14:37 ` howarth at nitro dot med dot uc dot edu
2010-05-08 14:39 ` howarth at nitro dot med dot uc dot edu
2010-05-08 14:55 ` howarth at nitro dot med dot uc dot edu
2010-05-08 20:08 ` howarth at nitro dot med dot uc dot edu
2010-05-08 20:14 ` howarth at nitro dot med dot uc dot edu
2010-05-25 0:29 ` mrs at gcc dot gnu dot org
2010-06-06 10:50 ` dominiq at lps dot ens dot fr
2010-06-06 13:46 ` dominiq at lps dot ens dot fr
2010-06-06 20:23 ` dominiq at lps dot ens dot fr
2010-06-14 13:14 ` howarth at nitro dot med dot uc dot edu
2010-07-17 22:55 ` steven at gcc dot gnu dot org
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=20100501152603.20705.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).