update toolchain packages for bionic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
gcc-7-cross (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Invalid
|
Undecided
|
Unassigned | ||
gcc-7-cross-ports (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Invalid
|
Undecided
|
Unassigned | ||
gcc-8 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This is a follow-up to LP: #1814369. I'd like to update the toolchain packages in bionic, to the state which we have in the eoan release in October 2019 (gcc-7), and in focal (gcc-8).
- gcc-8, update to the gcc-8.3 branch
- gcc-7, updates to the gcc-7.5.0 release
- corresponding gcc-cross packages
The package builds are prepared in
https:/
[Impact]
Provide an upstream release for GCC 7.5, and update GCC 8 to the 8.3
branch
[Regression Potential]
There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found.
[Test Case]
No regressions in the GCC test suite, and no regressions in the test
rebuild of the main component of the archive (all architectures)
As a test, a complete archive rebuild was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-
[Validation]
Analyze the build logs for regressions.
For the cross builds, just make sure that the packages build using
the updated sources.
Summary of the test rebuilds:
https:/
https:/
The first one is a reference build, the second one the test rebuild with the updated components.
There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will
be disabled in a follow-up upload.
description: | updated |
Changed in gcc-7 (Ubuntu): | |
status: | New → Fix Released |
Changed in gcc-8 (Ubuntu): | |
status: | New → Fix Released |
Changed in gcc-7-cross (Ubuntu Eoan): | |
status: | New → Invalid |
Changed in gcc-7-cross-ports (Ubuntu Eoan): | |
status: | New → Invalid |
Changed in gcc-7-cross-ports (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-7-cross (Ubuntu): | |
status: | New → Invalid |
Hello Matthias, or anyone else affected,
Accepted gcc-8 into eoan-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ gcc-8/8. 3.0-26ubuntu1~ 19.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- eoan to verification- done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- eoan. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.