public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/2192 Date: Wed, 21 Mar 2001 05:56:00 -0000 [thread overview] Message-ID: <20010321135601.19908.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/2192; it has been noted by GNATS. From: neil@gcc.gnu.org To: bmrevet@igr.fr, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/2192 Date: 21 Mar 2001 13:46:46 -0000 Synopsis: compilation of GToolkit gtoolkit-0.9.4] under Red HAT 7.0 State-Changed-From-To: open->closed State-Changed-By: neil State-Changed-When: Wed Mar 21 05:46:46 2001 State-Changed-Why: If you already submitted the bug and didn't get an answer, that means it's still open. Resubmitting just slows us all down, so I'm closing this. Also, you did not follow the instructions GCC gave you, which makes this bug report useless. <<Please submit a full bug report. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.>> You could try a recent snapshot of GCC - there have been several Objective C fixes made. At least, it looks like you're using Objective C, so you should file the bug reports under the ObjC category and not the C category. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2192&database=gcc
reply other threads:[~2001-03-21 5:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010321135601.19908.qmail@sourceware.cygnus.com \ --to=neil@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).