From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22760 invoked by alias); 28 Jul 2011 12:07:03 -0000 Received: (qmail 22741 invoked by uid 22791); 28 Jul 2011 12:07:02 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Jul 2011 12:06:48 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1QmPMV-0007CR-Tf for gdb@sourceware.org; Thu, 28 Jul 2011 08:06:47 -0400 Date: Thu, 28 Jul 2011 12:07:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sourceware.org Subject: py-breakpoint.c fails to compile with MinGW GCC Reply-to: Eli Zaretskii 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/msg00107.txt.bz2 The error message is: ./python/py-breakpoint.c:1019: error: initializer element is not constant ./python/py-breakpoint.c:1019: error: (near initialization for `breakpoint_objec t_type.tp_new') This is with MinGW GCC 3.4.2 (yes, old, but it worked fine for me until now). I have Python 2.7.1 installed on that machine. Removing the last element of the initializer, i.e. this line: PyType_GenericNew /* tp_new */ allows py-breakpoint.c to compile. Is this a bug in GCC, in GDB, in Python, or in my setup? TIA