public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47111] New: mips-rtems: redefinition of NO_IMPLICIT_EXTERN_C Date: Wed, 29 Dec 2010 12:54:00 -0000 [thread overview] Message-ID: <bug-47111-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47111 Summary: mips-rtems: redefinition of NO_IMPLICIT_EXTERN_C Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: amylaar@gcc.gnu.org Blocks: 44756 Host: x86_64-pc-linux-gnu Target: mips-rtems In file included from ./tm.h:20:0, from ../../../gcc/gcc/gensupport.c:24: ../../../gcc/gcc/config/rtems.h:21:0: error: "NO_IMPLICIT_EXTERN_C" redefined [-Werror] ../../../gcc/gcc/config/mips/elf.h:51:0: note: this is the location of the previous definition cc1: all warnings being treated as errors make[2]: *** [build/gensupport.o] Error 1
next reply other threads:[~2010-12-29 12:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-29 12:54 amylaar at gcc dot gnu.org [this message] 2010-12-31 10:29 ` [Bug target/47111] " amylaar at gcc dot gnu.org 2010-12-31 10:34 ` amylaar at gcc dot gnu.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=bug-47111-4@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).