Dynamically-generated C stored in SVN is breaking our distribution because life is awful (was Re: F28 System Wide Change: GCC8)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2018-02-19 at 22:57 -0800, Adam Williamson wrote:
> On Tue, 2018-01-09 at 21:51 +0100, Jakub Jelinek wrote:
> > On Tue, Jan 09, 2018 at 07:50:10PM +0000, Stephen Gallagher wrote:
> > > > Well, true, but then just like every year, we'll wind up doing a lot of
> > > > the spadework of fixing things to build with the new GCC. And probably
> > > > at first some critical things will fail to build and that'll mess up
> > > > the stability of the distro for a couple of weeks. I guess if everyone
> > > > else is still loving that grind, hey.
> > > > 
> > > 
> > > 
> > > This is the cost of being "First". Fedora has long enjoyed a tight coupling
> > > with the GCC upstream. It's a symbiosis: they use our mass-rebuild to help
> > > identify any issues before GCC goes stable and in turn Fedora gets to have
> > > the newest compiler features before anyone else.
> > 
> > To be fair, Ubuntu (or Debian or both, dunno) has already performed test mass
> > rebuilds with GCC 8 prerelease some time ago and OpenSUSE usually performs them
> > roughly at the same time as we do.  We are likely the first one or one of
> > the first ones to deploy it as a stable compiler in the distro and it is
> > mutually beneficial both for the distro and for GCC.
> 
> Just for the record, it is now 11pm the day before we are supposed to
> branch Fedora 28, and I have spent the whole evening fixing
> OpenColorIO's Python bindings to build with GCC 8:
> 
> https://github.com/imageworks/OpenColorIO/pull/518
> 
> only to find that it fails to build on i686 because since pdftex got
> rebuilt with GCC 8 (OK, haven't confirmed that yet, but it's the most
> obvious suspect), it's segfaulting:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=25176488
> 
> Also noted by QuLogic trying to build R-htmltools:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=25173683
> 
> So now I am running the build in an i686 mock so I can shell into the
> mock and hopefully get a traceback of the pdftex crash and try to do
> *something* about fixing it.

So, here lies a hilarious tale of dynamic generation of entirely
undocumented C code using single-character variable names by a
ridiculously arcane build system tracked in Subversion:

https://bugzilla.redhat.com/show_bug.cgi?id=1546964

Excuse me while I go break some stuff.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux