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 driver/47676] error: field âOttybâ has incomplete type
Date: Thu, 10 Feb 2011 12:55:00 -0000 [thread overview]
Message-ID: <bug-47676-4-HZfmMnR72h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47676-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47676
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011.02.10 12:43:35
Ever Confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-10 12:43:35 UTC ---
I don't know why you think this is a gcc bug but please follow the instructions
at http://gcc.gnu.org/bugs/ and provide preprocessed source.
This is more likely to be a bug in your code. Even if it's a problem with the
ncurses/term.h header, that's not a GCC bug.
next prev parent reply other threads:[~2011-02-10 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 12:43 [Bug driver/47676] New: " ak0030470 at techmahindra dot com
2011-02-10 12:55 ` redi at gcc dot gnu.org [this message]
2011-02-10 12:58 ` [Bug driver/47676] " ak0030470 at techmahindra dot com
2011-02-10 14:39 ` redi at gcc dot gnu.org
2011-02-23 13:36 ` 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-47676-4-HZfmMnR72h@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: 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).