Understanding the Fedora GCC versions / release cycle

asked 2019-03-22 15:02:13 -0600

svenevs gravatar image


Been using Fedora since fc19, and had never really noticed that the GCC versions don't actually mirror "actual GCC releases" until today. I recently upgraded to Fedora 29, but had forgotten that I was in the middle of patching a build system that is affected by a GCC bug related to unnecessary warnings about LTO stuffs.

I remembered that the Fedora 27 GCC version was 7.3.1, but when looking around the official releases on GNU I came to learn that they don't actually officially tag patch releases. This definitely wasn't a bottleneck...but I really just became rather curious as to how the GCC versions are chosen given the lack of official tags. For example, right now on a fully upgraded Fedora 29 I have gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC)

I found this commit: https://github.com/gcc-mirror/gcc/com... (linking to GitHub for UI convenience).

So is the protocol basically when they update gcc/BASE-VER for the major branch (e.g. in this case gcc-8-branch) it will be repackaged (provided that the distribution in question is actively being maintained)? Seems like too much of a coincidence that the commit linked above happened the day before the fc29 release ;)

Sorry if this is a total from-left-field question, I couldn't find any official documentation on what the protocol is. Did I get it right?

edit retag flag offensive close merge delete