Date: Tue, 7 Jan 2020 10:00:34 -0500 From: Ed Maste <emaste@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Gcc 4.2.1 to be removed before FreeBSD 13, a firm timeline Message-ID: <CAPyFy2CbJKCNTPTLvkBLue6EeguVvdYO6L4=1U2EshY6FtJa3w@mail.gmail.com> In-Reply-To: <CANCZdfr-=DUVJ7Bd9SgA9kyQ3TKZefOZfu76TJ9XgRgo2OJHWQ@mail.gmail.com> References: <CANCZdfrZ-C37c7Eso7NrtMG5_kv3T9qO3c3k8xcgEeTCrY3nQg@mail.gmail.com> <CANCZdfr-=DUVJ7Bd9SgA9kyQ3TKZefOZfu76TJ9XgRgo2OJHWQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 6 Jan 2020 at 01:56, Warner Losh <imp@bsdimp.com> wrote: > > Third, we should move up the removal of gcc 4.2.1 to 2020-02-29 as well, > with a deadline of 2020-01-31 for someone to publish a github branch that > removes gcc for wide-spread testing. An exception to the gcc rule should be > made for libunwind until that can be sorted out. I've been staging my gcc 4.2.1 deorbit work at https://github.com/emaste/freebsd/tree/deorbit-gcc; I'll force-push it on occasion after related changes make it into svn. Removing contrib/gcc and contrib/gcclibs is trivial; there may be some iteration on correctly removing the build infrastructure.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CbJKCNTPTLvkBLue6EeguVvdYO6L4=1U2EshY6FtJa3w>