From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
gdb@sourceware.org
Subject: Re: py-breakpoint.c fails to compile with MinGW GCC
Date: Thu, 28 Jul 2011 15:37:00 -0000 [thread overview]
Message-ID: <m3y5ziwh5k.fsf@redhat.com> (raw)
In-Reply-To: <20110728151915.GU1988@adacore.com> (Joel Brobecker's message of "Thu, 28 Jul 2011 08:19:15 -0700")
Joel Brobecker <brobecker@adacore.com> writes:
>> 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...
Maybe older versions of Python did not tag with dllimport, or these
particular pieces. I don't have access to a windows box locally, so I'm
just guessing/speculating.
Cheers
Phil
next prev parent reply other threads:[~2011-07-28 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 12:07 Eli Zaretskii
2011-07-28 14:54 ` Phil Muldoon
2011-07-28 15:01 ` Tom Tromey
2011-07-28 15:19 ` Joel Brobecker
2011-07-28 15:37 ` Phil Muldoon [this message]
2011-07-28 15:44 ` Tom Tromey
2011-07-28 16:11 ` Kai Tietz
2011-07-28 16:17 ` Eli Zaretskii
2011-07-28 16:46 ` Tom Tromey
2011-07-28 17:07 ` Eli Zaretskii
2011-07-29 3:04 ` Chris Sutcliffe
2011-07-29 6:13 ` Eli Zaretskii
2011-07-28 16:13 ` Eli Zaretskii
2011-07-28 16:25 ` Joel Brobecker
2011-07-28 16:48 ` Tom Tromey
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=m3y5ziwh5k.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=tromey@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