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

>Number:         3516
>Category:       c
>Synopsis:       libIDL consts  are broken.  stddef.h line 199 TOK_LONG, TOK_SHORT expected
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 01 10:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Shaun savage
>Release:        gcc-3.0
>Organization:
>Environment:
RH7.1 with gcc-3.0 (./configure --prefix=/usr; make bootstrap)
>Description:
It started trying to compile Mozilla 0.9.2. I was getting const out of bounds. in the idl file it was "2" or "1 << 2". then I started debugging libIDL-0.6.so

I used RH7.1 ORBit-0.5.7 src.rpm and tried to compile it.  I stated getting errors with that libIDL.  Then I changed libIDL to debug (-g) and traced into it.  I got lost in yyparse(); until the error 
"/usr/lib/gcc-lib/i686-gnu-linux-pc/3.0/include/stddef.h  parse error TOK_SHORT or TOK_LONG expected"

I realize that this ?bug? is not well defined. 

If RedHat used a gcc-2.95 I would not have to  use 3.0 (I would anyway).
It would be great if you made a gcc-3.0 rpm so people could upgrade to a good compile with out these type of problems

Shaun savage
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-01 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01 10:56 savages [this message]
2001-12-01 21:03 rodrigc
2001-12-01 21:06 rodrigc

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=20010701175154.9403.qmail@sourceware.cygnus.com \
    --to=savages@zae.att.ne.jp \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).