On Jul 17 06:02, JonY wrote: > On 7/16/2014 15:02, Corinna Vinschen wrote: > > Hi JonY, > > > > On Jul 15 16:39, Corinna Vinschen wrote: > >> On Jul 15 21:55, JonY wrote: > >>> On 7/15/2014 21:08, Corinna Vinschen wrote: > >>>>> > >>>>> FWIW, the problem disappears if I revert gcc-core and libgcc1 to > >>>>> 4.8.2-2. > >>>> > >>>> JonY, do you have a chance to have a look into this issue? > >>>> > >>> > >>> Sorry, I have been busy these few weeks, but I am well aware that there > >>> is a problem with one of the libgcc changes, but has yet to investigate > >>> it. > >>> > >>> I believe Jon Turney has looked into it somewhat. > >> > >> Sounds good. Thanks in advance. > > > > Yesterday I asked my collegues to take a stab at the issue and one of > > them, DJ Delorie, came up with a libgcc patch already. It hasn't been > > sent upstream yet. Can we give it a try, perhaps by creating a new > > libgcc DLL, please? > > > > Thanks, I'll get to it this weekend, should I make the new gcc an > experimental version? Or is just the libgcc binary required?
It's the libgcc DLL which gives us grief, so a new libgcc package is sufficent, afaics. We should check if this DLL fixes the problem and then make it "curr" soon, I think. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpxym5D6k6uG.pgp
Description: PGP signature
