This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: 64bit: C++ templates
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 3 Jun 2013 10:08:36 +0200
- Subject: Re: 64bit: C++ templates
- References: <516CDE32 dot 5000206 at users dot sourceforge dot net> <516F5F89 dot 40600 at users dot sourceforge dot net> <518C9018 dot 9030606 at users dot sourceforge dot net> <CAEwic4aPQHUChVWui6h0FctFkHXh3A0zwh1On50cJRE=SV1UeA at mail dot gmail dot com> <CAEwic4ZAy++TifyZR=XZnD_xahM0GOdO-XREvY6ZdKGQRc+ykA at mail dot gmail dot com> <20130516082534 dot GB11933 at calimero dot vinschen dot de> <5199C9DB dot 8040406 at users dot sourceforge dot net> <20130520092614 dot GA31140 at calimero dot vinschen dot de> <51AC2303 dot 8040409 at users dot sourceforge dot net>
- Reply-to: cygwin-developers at cygwin dot com
On Jun 3 00:00, Yaakov (Cygwin/X) wrote:
> On 2013-05-20 04:26, Corinna Vinschen wrote:
> >On May 20 01:59, Yaakov (Cygwin/X) wrote:
> >>This seems to fix harfbuzz wrt gtk2; gtk3 still isn't working, but
> >>I'm not sure it's related yet.
> >
> >Dunno, but more info on that might help my collegues to fix the issue.
>
> WRT gtk3, the culprit was actually an apparent LTO bug in
> libcairo-gobject (a thin GObject wrapper for libcairo which gtk2.0
> does not use); any call to CAIRO_GOBJECT_TYPE_* seems to go to la-la
> land and SEGV. Recompiling libcairo-gobject without -flto allows
> gtk3 to work. (Strangely enough, the much larger libcairo itself
> seems to work even with -flto.) As for fixing LTO, well, that will
> have to be a different discussion; at least we can move forward
> again with the GNOME stack.
I'm glad to read that.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat