X-Recipient: archive-cygwin AT delorie DOT 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=OFTP0Rz14Kr4jt+BNa6mQIMkYXd3XquF8MkkGYqUxpl/X/HLthuX1
	MetBKya4m+OCHaQ4EP5HxD1l+p+0TiH/UkHTBelFv/lzSzRWzbDiJY94/OcFVth9
	K+KYRCoF3AskY49zRHakN3IKoCYPD8VTr9Xai4EPiyEKpUm5r8YHmI=
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=Ry+6pr7sZrhizs1aC55xFgIfEW0=; b=FiDEetTrz/1jsvRrKWTn/drGLD0R
	hIW5qIMZ5qV4uOw8xuTivUu7g2uX5SXVsEvqzf3x0rzNyjLpseLtGWxLLLl2V+X9
	d2Jgkvt9AB6jDST2GlRcSkkQbZqtGO1OouYRlppiDx5GAxnaRDgWS8YUY7CvlGIk
	eBQ4ZZUjUre6/2U=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPAM_SUBJECT,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Jean-Pierre Flori <jpflori AT gmail DOT com>
Subject: Re: python aborts
Date: Thu, 7 Nov 2013 21:53:04 +0000 (UTC)
Lines: 67
Message-ID: <l5h240$esa$2@ger.gmane.org>
References:  <20130725091741 DOT GA20682 AT calimero DOT vinschen DOT de>	<51F0FB68 DOT 90904 AT gmail DOT com> <51F103CB DOT 20904 AT gmail DOT com>	<20130725151410 DOT GB6932 AT ednor DOT casa DOT cgf DOT cx> <51F14DE9 DOT 7050702 AT gmail DOT com>	<20130725172007 DOT GC6019 AT ednor DOT casa DOT cgf DOT cx> <51F1A3AA DOT 5040804 AT gmail DOT com>	<20130726031048 DOT GD1954 AT ednor DOT casa DOT cgf DOT cx>	<20130828035943 DOT GA6973 AT ednor DOT casa DOT cgf DOT cx> <l5efta$5qf$1 AT ger DOT gmane DOT org>	<20131107132020 DOT GA16306 AT calimero DOT vinschen DOT 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.
> 
Thanks!

> That won't happen, probably, since practically all crucial parts of the
> distro are linked dynamically against libgcc.  Just providing and using
> a new libgcc should be sufficient, except in rare cases.  AFAIU.
> 
Sure, hopefully all or most packages link to a shared cyggcc_s.dll and 
just rebuilding gcc should be enough.

My last issue was that when I built gcc, the similar library was named 
something like cyggcc_sjs.dll so the few native Cygwin packages I still 
used or linked to could still load the bad cyggcc_s.dll and make Python 
abort!

Thanks for the support,
Best,
JP


--
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