public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
@ 2001-12-01 21:03 rodrigc
0 siblings, 0 replies; 3+ messages in thread
From: rodrigc @ 2001-12-01 21:03 UTC (permalink / raw)
To: gcc-bugs, gcc-gnats, gcc-prs, nobody, savages, support
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
@ 2001-12-01 21:06 rodrigc
0 siblings, 0 replies; 3+ messages in thread
From: rodrigc @ 2001-12-01 21:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/3516; it has been noted by GNATS.
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
Cc:
Subject: Re: c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
Date: 2 Dec 2001 05:03:22 -0000
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected
@ 2001-07-01 10:56 savages
0 siblings, 0 replies; 3+ messages in thread
From: savages @ 2001-07-01 10:56 UTC (permalink / raw)
To: gcc-gnats; +Cc: support
>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:
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-12-02 5:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-01 21:03 c/3516: libIDL consts are broken. stddef.h line 199 TOK_LONG, TOK_SHORT expected rodrigc
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 21:06 rodrigc
2001-07-01 10:56 savages
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).