X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=F5Q8tgDF+0chJ+Totr5qwP2cj/W8kzVGTekEVgEsIraR6RkO8hcuw
	478fhXuYTKXcq1CHaJ7Tc1IgpW7TrPAqHLYpwanSfnY86dmWFZcQLVt95RFgGEtH
	ztfUAF8ih1ClOTRwFQd2A7LGuxEJTiD288UwnzFMDWdPyi5a300SfY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=8ok83Z6MuZQdZ/d0VD0k/bn8/hc=; b=T5LLawiMibfVTM4kQVpZzFdcP6Ek
	Odqw9olrtsoNwdzPvTkrl245vVQG5IfVf7QlFy8MQg/J3DqRm2VZjDnP75oEr/T8
	7cIdu/QYTOlVOPYzjREi+jWAr66Zny/4aAU4y7mKvHsfosyR1qEoL/ZSZxTIS9qz
	yj7HRkA9ZbeE2j8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin@cygwin.com
From: Jean-Pierre Flori <jpflori@gmail.com>
Subject: Re: python aborts
Date: Fri, 8 Nov 2013 16:40:02 +0000 (UTC)
Lines: 53
Message-ID: <l5j452$5bn$1@ger.gmane.org>
References:  <20130725091741.GA20682@calimero.vinschen.de>	<51F0FB68.90904@gmail.com> <51F103CB.20904@gmail.com>	<20130725151410.GB6932@ednor.casa.cgf.cx> <51F14DE9.7050702@gmail.com>	<20130725172007.GC6019@ednor.casa.cgf.cx> <51F1A3AA.5040804@gmail.com>	<20130726031048.GD1954@ednor.casa.cgf.cx>	<20130828035943.GA6973@ednor.casa.cgf.cx> <l5efta$5qf$1@ger.gmane.org>	<20131107132020.GA16306@calimero.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2)
X-IsSubscribed: yes

Le Thu, 07 Nov 2013 14:20:20 +0100, Corinna Vinschen a écrit :

> On Nov  6 22:30, Jean-Pierre Flori wrote:
>> Dear all,
>> 
>> Le Tue, 27 Aug 2013 23:59:43 -0400, Christopher Faylor a écrit :
>> 
>> > On Thu, Jul 25, 2013 at 11:10:48PM -0400, Christopher Faylor wrote:
>> >>On Fri, Jul 26, 2013 at 06:16:10AM +0800, JonY wrote:
>> >>>On 7/26/2013 01:20, Christopher Faylor wrote:
>> >>>> On Fri, Jul 26, 2013 at 12:10:17AM +0800, JonY wrote:
>> >>>>> On 7/25/2013 23:14, Christopher Faylor wrote:
>> >>>>>>
>> >>>>>> I'm still a (silent) gcc maintainer so I can presumably accept
>> >>>>>> this patch.
>> >>>>>>
>> >>>>>> Are there outstanding patches that need attention?  If so,
>> >>>>>> please send URLs from the gcc-patches archive here so that I can
>> >>>>>> attend to them.
>> >>>>>>
>> >>>>>>
>> >>>>> This libgcc patch, and some minor patches at
>> >>>>> http://gcc.gnu.org/ml/gcc-patches/2013-07/msg00416.html.
>> >>>>>
>> >>>>> There are some others from Yaakov's gcc builds, but let's start
>> >>>>> with smaller patches first.
>> >>>> 
>> >>>> It will probably be a couple of days before I can give these
>> >>>> adequate attention.
>> >>>> 
>> >>>> Ok to submit your name as an upstream approver, JonY?
>> >>>> 
>> >>>> 
>> >>>I have not approved any patches for GCC, not sure if I can act as
>> >>>approver. Kai usually approves and commits any mingw* related gcc
>> >>>patches but he is not in currently.
>> >>
>> >>Uh, yeah.  AFAIK, you aren't listed as a package approver so it would
>> >>be very difficult for you to approve anything.
>> >>
>> >>Ok, nevermind.
>> > 
>> > Did this ever get resolved?  Did Kai apply the patches?
>> > 
>> > cgf
>> 
>> Any progress on this very nasty libgcc bug?
> 
> I pinged the upstream maintainer who probably wasn't aware of this yet.

By the way, i found:
* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57680
which looks very similar.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

