Bug 1580076 - Update cross-gcc to gcc 8 GA
Summary: Update cross-gcc to gcc 8 GA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cross-gcc
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Howells
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-19 21:18 UTC by Peter Robinson
Modified: 2018-07-31 18:01 UTC (History)
4 users (show)

Fixed In Version: cross-gcc-8.1.1-3.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-31 18:01:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Robinson 2018-05-19 21:18:52 UTC 
Update cross-gcc to the 8.1 GA release in Fedora 28+, possibly might need a sync up of cross-binutils as well, so the cross compiler stack matches the Fedora 28 main Fedora toolchain stack.
Comment 1 Alexey Brodkin 2018-07-09 15:30:57 UTC 
cross-binutils are 2.30-based for quite some time now, see https://src.fedoraproject.org/cgit/rpms/cross-binutils.git/commit/?id=197b26143198017c54fdc43eb9e613de91f547b3

And indeed bumping og cross-gcc makes perfect sense.
Comment 2 Fedora Update System 2018-07-13 08:56:36 UTC 
cross-gcc-8.1.1-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9a0d2245d5
Comment 3 Fedora Update System 2018-07-16 20:29:00 UTC 
cross-gcc-8.1.1-3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-9a0d2245d5
Comment 4 Fedora Update System 2018-07-31 18:01:24 UTC 
cross-gcc-8.1.1-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.