public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, savages@zae.att.ne.jp, support@redhat.com
Subject: Re: c/3516: libIDL consts  are broken.  stddef.h line 199 TOK_LONG, TOK_SHORT expected
Date: Sat, 01 Dec 2001 21:03:00 -0000	[thread overview]
Message-ID: <20011202050322.32644.qmail@sourceware.cygnus.com> (raw)

Synopsis: libIDL consts  are broken.  stddef.h line 199 TOK_LONG, TOK_SHORT expected

State-Changed-From-To: open->closed
State-Changed-By: rodrigc
State-Changed-When: Sat Dec  1 21:03:21 2001
State-Changed-Why:
    This looks more like a Red Hat packaging problem than
    a gcc problem.  Refer to http://gcc.gnu.org/bugs.html for
    how to report a GCC problem.
    
    For Red Hat specific problems, you should submit bugs
    to Red Hat at http://bugzilla.redhat.com/bugzilla/

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3516&database=gcc


             reply	other threads:[~2001-12-02  5:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 21:03 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01 21:06 rodrigc
2001-07-01 10:56 savages

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=20011202050322.32644.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=savages@zae.att.ne.jp \
    --cc=support@redhat.com \
    /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).