public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/52168] New: fixinclude test failure for complex.h on netbsd Date: Wed, 08 Feb 2012 09:29:00 -0000 [thread overview] Message-ID: <bug-52168-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52168 Bug #: 52168 Summary: fixinclude test failure for complex.h on netbsd Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: redi@gcc.gnu.org Bootstrapped using the default BSD sed, awk etc. complex.h /home/jwakely/src/full/gcc/fixincludes/tests/base/complex.h differ: char 839, line 41 *** complex.h Wed Feb 8 10:21:00 2012 --- /home/jwakely/src/full/gcc/fixincludes/tests/base/complex.h Mon Nov 7 09:52:51 2011 *************** *** 38,43 **** #if defined( SOLARIS_COMPLEX_CXX_CHECK ) #ifdef __cplusplus extern "C" { ! #endif#ifdef __cplusplus } ! #endif#endif /* SOLARIS_COMPLEX_CXX_CHECK */ --- 38,45 ---- #if defined( SOLARIS_COMPLEX_CXX_CHECK ) #ifdef __cplusplus extern "C" { ! #endif ! #ifdef __cplusplus } ! #endif ! #endif /* SOLARIS_COMPLEX_CXX_CHECK */ There were fixinclude test FAILURES
next reply other threads:[~2012-02-08 9:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-08 9:29 redi at gcc dot gnu.org [this message] 2012-02-08 10:20 ` [Bug other/52168] " rguenth at gcc dot gnu.org 2012-02-09 0:38 ` redi at gcc dot gnu.org 2012-02-09 9:21 ` jakub at gcc dot gnu.org 2012-02-09 12:20 ` redi at gcc dot gnu.org 2012-02-09 12:25 ` redi at gcc dot gnu.org 2012-02-09 21:32 ` redi at gcc dot gnu.org 2012-02-09 21:58 ` redi at gcc dot gnu.org 2012-02-09 22:03 ` redi at gcc dot gnu.org 2014-11-16 6:41 ` richard at netbsd dot org 2014-11-16 14:29 ` redi 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-52168-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).