This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
- From: savages at zae dot att dot ne dot jp
- Date: 1 Jul 2001 17:51:54 -0000
- Cc: support at redhat dot com
- Reply-To: savages at zae dot att dot ne dot jp
>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: