= System Wide Change: GCC7 = https://fedoraproject.org/wiki/Changes/GCC7
Change owner(s): * Jakub Jelínek <jakub AT redhat DOT com>
Switch GCC in Fedora 26 to 7.x.y, rebuild all packages with it, or optionally rebuild just some packages with it and rebuild all packages only in Fedora 27.
== Detailed Description == GCC 7 is currently in stage3, will move to stage4 on January 19th, in prerelease state with only regression bugfixes and documentation fixes allowed. The release will happen probably in the middle of April. We are working on scratch gcc rpms and will perform a test mass rebuild.
== Scope == All packages should be rebuilt with the new gcc once it hits f26, or, if there is not enough time for that, just all packages built after the new gcc hits the buildroots.
* Proposal owners: Build gcc in f26, rebuild packages that have direct dependencies on exact gcc version (libtool, llvm, gcc-python-plugin, odb).
* Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at http://gcc.gnu.org/gcc-7/porting_to.html and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
* Release engineering: Organize a mass rebuild, either in f26 or in f27
* Policies and guidelines: No policies need to be changed
On Tue, Jan 10, 2017 at 10:28:37AM +0100, Jan Kurik wrote:
- Other developers:
First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at http://gcc.gnu.org/gcc-7/porting_to.html and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
It seems like this link is broken.
Rich.
On Wed, 2017-01-11 at 04:17 +0000, Richard W.M. Jones wrote:
On Tue, Jan 10, 2017 at 10:28:37AM +0100, Jan Kurik wrote:
- Other developers:
First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at http://gcc.gnu.org/gcc-7/porting_to.html and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
It seems like this link is broken.
Well, https://gcc.gnu.org/gcc-6/porting_to.html exists, and so does https://gcc.gnu.org/gcc-5/porting_to.html . Presumably when the 7 porting guide is done, it'll be there.
On Wed, Jan 11, 2017 at 04:17:56AM +0000, Richard W.M. Jones wrote:
On Tue, Jan 10, 2017 at 10:28:37AM +0100, Jan Kurik wrote:
- Other developers:
First few days/weeks just voluntary rebuilds using the new system gcc, if things fail, look at http://gcc.gnu.org/gcc-7/porting_to.html and fix bugs in packages or, if there is a gcc bug or suspected gcc bug, analyze and report.
It seems like this link is broken.
It is where the porting to will appear when it is written. So far just the gcc-7/changes.html link works (but is still very incomplete). porting_to.html is usually written in second half of January.
Jakub
On Tue, Jan 10, 2017 at 2:28 AM, Jan Kurik jkurik@redhat.com wrote:
= System Wide Change: GCC7 = https://fedoraproject.org/wiki/Changes/GCC7
Change owner(s):
- Jakub Jelínek <jakub AT redhat DOT com>
Switch GCC in Fedora 26 to 7.x.y, rebuild all packages with it, or optionally rebuild just some packages with it and rebuild all packages only in Fedora 27.
== Detailed Description == GCC 7 is currently in stage3, will move to stage4 on January 19th, in prerelease state with only regression bugfixes and documentation fixes allowed. The release will happen probably in the middle of April. We are working on scratch gcc rpms and will perform a test mass rebuild.
== Scope == All packages should be rebuilt with the new gcc once it hits f26, or, if there is not enough time for that, just all packages built after the new gcc hits the buildroots.
- Proposal owners:
Build gcc in f26, rebuild packages that have direct dependencies on exact gcc version (libtool, llvm, gcc-python-plugin, odb).
Now, that plugins are kept in a directory that is just the major part of the version number, I will make it so that odb no longer has a Requires on the exact of gcc.
devel@lists.stg.fedoraproject.org