Mail Archives: cygwin/2013/11/07/08:21:00
--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Nov 6 22:30, Jean-Pierre Flori wrote:
> Dear all,
>=20
> Le Tue, 27 Aug 2013 23:59:43 -0400, Christopher Faylor a =C3=A9crit=C2=A0:
>=20
> > 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.
> >>>>=20
> >>>> It will probably be a couple of days before I can give these adequate
> >>>> attention.
> >>>>=20
> >>>> Ok to submit your name as an upstream approver, JonY?
> >>>>=20
> >>>>=20
> >>>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.
> >=20
> > Did this ever get resolved? Did Kai apply the patches?
> >=20
> > cgf
>=20
> Any progress on this very nasty libgcc bug?
I pinged the upstream maintainer who probably wasn't aware of this yet.
> I've been struggling with random python aborts in the last past weeks,=20
> pointing more or less to verifyable_object_isvalid with quite unhelpful=
=20
> backtraces, when I finally found this report and a potential fix at=20
> http://cygwin.com/ml/cygwin/2013-07/msg00528.html.
> See also http://cygwin.com/ml/cygwin/2013-08/msg00201.html.
> The fix seems to do the trick for me though I cannot really rely on any=
=20
> Cygwin part linked with cyggcc_s.dll unless I recompile it.
> Any plan to trigger a complete rebuild of Cygwin packages using a fixed=
=20
> GCC? :)
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.
Corinna
--=20
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBAgAGBQJSe5OUAAoJEPU2Bp2uRE+g/UwP/1rFM2GZRqV0nPl/NlIm85Rz
daa7nYTCB8Hj1/DJTL2+91+SdvbZ2go93aan3hyIiWRG+tgPKowIyCAIWjfZJ+Ur
eq8GKgovXFJIQ4HzVcx2YUpUnkq0+9vyq05fV2DZc2NS1DSLNvedwxtg2+oYS4lt
IZjmWH1FNDspT8pfC/7hSOYkfBveaycH1UHGUHNIyR4DNK+mRBmDU+tXfUYNNmCJ
DdQD9iShpnc+y5eW6Gi7+Mxa1NxFnvf6VM3o4PDOqN2bOlukAX1cC6YEr4vEoNwm
Pqweue27d2EW2CuBELcvoJDrAJFSdl5gFKWqv/tfXc3090qA6MJ04hYP8ngo6YY2
iC6H4Hh2veXh1VDtXQh/+63MyN/ySTn81lwuT8mq+N5XSuPKK4wy+mGgQH4JddT2
20nJjaBiSfpv7XHZH6x5aqAd3APOooGKbW+LSndRhuKna0PrSf/FlimGK/NJdZPy
Joybu77SAsvVmkgW8RM6QsXOHnmT4sDH8do4UYl/4XBDb34aqt42BTA+s1OVUcX6
bohB2oZC8v8p4RXBSpIm0Bd6r+hQebtcP58altBWb1Pk3Lf/ThXvgT9ruIA8PNbu
RLzEdAuseE2nnywi9lPYTowmjmjt64/oKc44MaoD7ltD0ab4MChXlS0TZi3WlrqH
MtiB8SPqp3iNvdl0/E3O
=SPWZ
-----END PGP SIGNATURE-----
--G4iJoqBmSsgzjUCe--
- Raw text -