This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: py-breakpoint.c fails to compile with MinGW GCC

From: Joel Brobecker <brobecker at adacore dot com>
To: Tom Tromey <tromey at redhat dot com>
Cc: pmuldoon at redhat dot com, Eli Zaretskii <eliz at gnu dot org>, gdb at sourceware dot org
Date: Thu, 28 Jul 2011 08:19:15 -0700
Subject: Re: py-breakpoint.c fails to compile with MinGW GCC
References: <E1QmPMV-0007CR-Tf@fencepost.gnu.org> <m3vcumzc9x.fsf@redhat.com> <m3hb6678l0.fsf@fleche.redhat.com>

> Phil> I'm also unsure why some folks can compile ok (Dan in that email
> Phil> mentions he has been), and some can't.

It does compile for me too. Could be a compiler age issue?
Just wondering out loud - if we were to use a C++ compiler, would
it allow us to use non-static initializers like in this case?
I'm under the impression that C++ provides elaboration, so
non-static initialization should be do-able...

-- 
Joel

Follow-Ups:
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Phil Muldoon
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Tom Tromey

References:
- py-breakpoint.c fails to compile with MinGW GCC
  - From: Eli Zaretskii
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Phil Muldoon
- Re: py-breakpoint.c fails to compile with MinGW GCC
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]