public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/46929] New: Xutil.h and Complex - some trouble
@ 2010-12-13 19:12 lisp2d at lisp2d dot net
2010-12-13 19:14 ` [Bug c/46929] " pinskia at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: lisp2d at lisp2d dot net @ 2010-12-13 19:12 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46929
Summary: Xutil.h and Complex - some trouble
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: lisp2d@lisp2d.net
After including Xutil.h some trouble with name Complex
main.c:
//struct Complex{};
#include <X11/Xutil.h>
struct Complex{};
int main(void){return 0;}
>gcc main.c
main.c:3:8: error: expected ‘{’ before numeric constant
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug c/46929] Xutil.h and Complex - some trouble
2010-12-13 19:12 [Bug c/46929] New: Xutil.h and Complex - some trouble lisp2d at lisp2d dot net
@ 2010-12-13 19:14 ` pinskia at gcc dot gnu.org
0 siblings, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2010-12-13 19:14 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46929
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-12-13 19:14:39 UTC ---
There is a #define somewhere in the chain of X11/Xutil.h so this is not a GCC
issue.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-12-13 19:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-13 19:12 [Bug c/46929] New: Xutil.h and Complex - some trouble lisp2d at lisp2d dot net
2010-12-13 19:14 ` [Bug c/46929] " pinskia at gcc dot gnu.org
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).