I'm primarily referring to development compilation, not necessarily packaging. The default CFLAGS cause clang to fail 'out of the gate'. Given the popularity rise in the compiler, and the increase # of open tickets upstream around this issue, I think it prudent that we address. Not to change the whole packaging infrastructure, just so developers can install the tools and test their builds. Cheers, Tim ----- Original Message ----- > From: "Jakub Jelinek" <jakub@xxxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Cc: "Discussion of RPM packaging standards and practices for Fedora" <packaging@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Friday, May 30, 2014 4:03:57 AM > Subject: Re: fedoras default cflags & clang > > On Fri, May 30, 2014 at 10:25:28AM +0200, Ralf Corsepius wrote: > > On 05/29/2014 10:28 PM, Tim St Clair wrote: > > >I've been seeing this bug crop up in many circles: > > >https://bugzilla.redhat.com/show_bug.cgi?id=1099282 > > > > > >Many folks like to use clang as their primary compiler for various > > >reasons, is there anyone who knows a workaround or fix? > > > > I think FPC (and/or FESCO) should decide on whether we want to > > allow/disallow using clang for official Fedora rpms. > > https://fedorahosted.org/fesco/ticket/847 > http://meetbot.fedoraproject.org/fedora-meeting/2012-05-14/fesco.2012-05-14-17.00.log.html > > ? > > Jakub > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Cheers, Tim Freedom, Features, Friends, First -> Fedora https://fedoraproject.org/wiki/SIGs/bigdata -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
