On Nov 11 21:02, JonY wrote:
> On 11/11/2013 20:59, Corinna Vinschen wrote:
> >> I pinged the upstream maintainer who probably wasn't aware of this yet.
> >
> > The patche is checked in upstream. JonY, any chance for an updated
> > gcc toolchain soon?
> >
>
> The 4.8.2-1 release should already
On 11/11/2013 20:59, Corinna Vinschen wrote:
>> I pinged the upstream maintainer who probably wasn't aware of this yet.
>
> The patche is checked in upstream. JonY, any chance for an updated
> gcc toolchain soon?
>
The 4.8.2-1 release should already contain this patch.
signature.asc
Descr
On Nov 7 14:20, Corinna Vinschen wrote:
> On Nov 6 22:30, Jean-Pierre Flori wrote:
> > 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
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
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
>>>> 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
&
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, neverm
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 sti
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.
>
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
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 h
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
On Thu, Jul 25, 2013 at 06:54:03PM +0800, JonY wrote:
>On 7/25/2013 18:18, JonY wrote:
>> On 7/25/2013 17:17, Corinna Vinschen wrote:
>>> On Jul 25 01:36, Daniel Colascione wrote:
On 7/25/2013 12:11 AM, Daniel Colascione wrote:
> On 7/24/2013 11:55 PM, Daniel Colascione wrote:
>> Does
On 7/25/2013 18:18, JonY wrote:
> On 7/25/2013 17:17, Corinna Vinschen wrote:
>> On Jul 25 01:36, Daniel Colascione wrote:
>>> On 7/25/2013 12:11 AM, Daniel Colascione wrote:
On 7/24/2013 11:55 PM, Daniel Colascione wrote:
> Does that help at all? I only started seeing this problem after
On 7/25/2013 17:17, Corinna Vinschen wrote:
> On Jul 25 01:36, Daniel Colascione wrote:
>> On 7/25/2013 12:11 AM, Daniel Colascione wrote:
>>> On 7/24/2013 11:55 PM, Daniel Colascione wrote:
Does that help at all? I only started seeing this problem after I
recompiled
_wp.dll using
On Jul 25 01:36, Daniel Colascione wrote:
> On 7/25/2013 12:11 AM, Daniel Colascione wrote:
> > On 7/24/2013 11:55 PM, Daniel Colascione wrote:
> >> Does that help at all? I only started seeing this problem after I
> >> recompiled
> >> _wp.dll using gcc 4.7.3.
> >
> > Actually, this problem look
On 7/25/2013 12:11 AM, Daniel Colascione wrote:
> On 7/24/2013 11:55 PM, Daniel Colascione wrote:
>> Does that help at all? I only started seeing this problem after I recompiled
>> _wp.dll using gcc 4.7.3.
>
> Actually, this problem looks a lot like
> http://www.mail-archive.com/gcc@gcc.gnu.org/m
On 7/24/2013 11:55 PM, Daniel Colascione wrote:
> Does that help at all? I only started seeing this problem after I recompiled
> _wp.dll using gcc 4.7.3.
Actually, this problem looks a lot like
http://www.mail-archive.com/gcc@gcc.gnu.org/msg68316.html: neither Python nor
_wp links dynamically to
I just started seeing this problem myself --- on 1.7.22 release.
On 5/22/2013 5:31 AM, Corinna Vinschen wrote:
> On May 22 11:11, Denis Excoffier wrote:
>> Hello,
>>
>> With the current snapshot (20130521) on Windows XP, the following
>> fails (with an empty stackdump):
>>
>> % /usr/bin/python pyf
On May 22 11:11, Denis Excoffier wrote:
> Hello,
>
> With the current snapshot (20130521) on Windows XP, the following
> fails (with an empty stackdump):
>
> % /usr/bin/python pyfoo
> Abort (core dumped)
> % cat pyfoo
> import xml.sax
> xml.sax.make_parser()
> % cat python2.7.exe.stackdump
> Stac
Hello,
With the current snapshot (20130521) on Windows XP, the following fails
(with an empty stackdump):
% /usr/bin/python pyfoo
Abort (core dumped)
% cat pyfoo
import xml.sax
xml.sax.make_parser()
% cat python2.7.exe.stackdump
Stack trace:
Frame Function Args
% /usr/bin/python --version
21 matches
Mail list logo
