Bug 228919 - GCC 4.2.1 removal
Summary: GCC 4.2.1 removal
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Many People
Assignee: John Baldwin
URL: https://wiki.freebsd.org/ExternalGCC
Depends on: 229348 233361 233405 239851 233362 233751
Blocks: 233094
  Show dependency treegraph
Reported: 2018-06-12 08:47 UTC by Rodney W. Grimes
Modified: 2019-08-24 16:44 UTC (History)
9 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Rodney W. Grimes freebsd_committer 2018-06-12 08:47:49 UTC
GCC 4.2.1 removal before 12.0 branch
Comment 1 John Baldwin freebsd_committer freebsd_triage 2018-06-13 00:50:04 UTC
Outright removal might be hard to pull off, but I do hope to have at least one current 4.2.1 architecture migrated to external GCC instead for 12.0 (if not more than one).

I wrote some notes about this today at the indicated URL.
Comment 2 Mark Johnston freebsd_committer 2018-10-09 15:11:00 UTC
I presume that this won't make it for 12.0, so perhaps the "blocks" attribute should be cleared?
Comment 3 John Baldwin freebsd_committer freebsd_triage 2018-10-10 00:18:27 UTC
Yeah, I have a lingering issue I haven't debugged in base/gcc that causes --sysroot to still find libraries in /usr/lib that I haven't run to ground.
Comment 4 Ed Maste freebsd_committer 2019-08-14 13:04:48 UTC
Warner posted a timeline for GCC 4.2.1 removal at https://lists.freebsd.org/pipermail/freebsd-arch/2019-August/019674.html
Comment 5 Pedro F. Giffuni freebsd_committer 2019-08-15 15:49:37 UTC
Add the libssp removal exp-run (currently failing) as a reminder to get rid of it.