From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27115 invoked by alias); 28 Jul 2011 16:48:42 -0000 Received: (qmail 27106 invoked by uid 22791); 28 Jul 2011 16:48:41 -0000 X-SWARE-Spam-Status: No, hits=-7.5 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 16:48:27 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6SGmPcA017703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 12:48:25 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p6SGmP63008266; Thu, 28 Jul 2011 12:48:25 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p6SGmNGh009386; Thu, 28 Jul 2011 12:48:24 -0400 From: Tom Tromey To: Eli Zaretskii Cc: pmuldoon@redhat.com, gdb@sourceware.org Subject: Re: py-breakpoint.c fails to compile with MinGW GCC References: <83mxfye63t.fsf@gnu.org> Date: Thu, 28 Jul 2011 16:48:00 -0000 In-Reply-To: <83mxfye63t.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2011 19:13:10 +0300") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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/msg00118.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> Any hints as to what changes are needed? Is it just to move the call Eli> before PyType_Ready ? TIA Move each affected initializer out of the structure and into the function definition before the PyType_Ready call. See the link I provided to the Python docs, it has a worked example. Eli> Anyway, I think it's a pity we released 7.3 with this problem Eli> unsolved. Not many people care about GCC 3.4 any more. Tom