On Mon, May 13, 2019 at 07:42:16PM +0200, Dridi Boukelmoune wrote:
> On Tue, Jan 22, 2019 at 10:30 AM Jakub Jelinek <ja...@redhat.com> wrote:
> >
> > On Tue, Jan 22, 2019 at 10:02:22AM +0100, Miro Hrončok wrote:
> > > This is already happening, gcc was updated, I see bugs for gcc 9 related
> > > FTBFS being open. This is not a proper way to coordinate this kind of
> > > thing.
> >
> > I'm sorry, I forgot to create the every year feature request for GCC this
> > year and only realized that when I've successfully built first non-scratch
> > gcc 9 rpms. I believe Carlos has been mentioning GCC when F30 mass rebuild
> > has been discussed and GCC updates is something that has been done every
> > year in Fedora since at least Fedora 9 (we've skipped GCC 4.2 release back
> > in 2007).
> >
> > That said, a test mass rebuild has been performed (this year by Jeff Law)
> > and issues have been analyzed.
>
> Sorry for digging up this thread, but since this is a recurring change
> it appears that the mass rebuild is not enough by itself. As of today
> lcov doesn't work with GCC 9.x [1] and it would be nice if either:
>
> - gcc provided an option to use a previous gcov format when a new one
> lands (I understand it makes things more complicated)
No, we certainly don't want to diverge from gcc upstream here, and gcc
upstream doesn't have that.
> - the Fedora lcov spec would run `make test` in a %check section
lcov maintainers have been told they should use the json intermediate format
from gcov -i instead of trying to parse the binary data.
Jakub
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
