From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11066 invoked by alias); 28 Jul 2011 15:37:52 -0000 Received: (qmail 10971 invoked by uid 22791); 28 Jul 2011 15:37:51 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Jul 2011 15:37:37 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6SFbDnM025809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 11:37:13 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p6SFbBa5009719; Thu, 28 Jul 2011 11:37:12 -0400 From: Phil Muldoon To: Joel Brobecker Cc: Tom Tromey , Eli Zaretskii , gdb@sourceware.org Subject: Re: py-breakpoint.c fails to compile with MinGW GCC References: <20110728151915.GU1988@adacore.com> Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Thu, 28 Jul 2011 15:37:00 -0000 In-Reply-To: <20110728151915.GU1988@adacore.com> (Joel Brobecker's message of "Thu, 28 Jul 2011 08:19:15 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00111.txt.bz2 Joel Brobecker 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