Date: Fri, 30 Aug 2013 07:53:39 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: David Chisnall <theraven@FreeBSD.org> Cc: FreeBSD Current <current@FreeBSD.org>, Boris Samorodov <bsam@passap.ru>, toolchain@FreeBSD.org, "freebsd-current@freebsd.org CURRENT" <freebsd-current@FreeBSD.org>, "Sam Fourman Jr." <sfourman@gmail.com> Subject: Re: GCC withdraw Message-ID: <5220B1F3.1030807@freebsd.org> In-Reply-To: <ADADF693-B140-4C87-B464-9F139B31E7B5@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <CAOFF%2BZ3vbOgMO7T-BKZnhKte6=rFoGcdYcft5kpAgNH2my1JKg@mail.gmail.com> <DC41B4BD-159A-408B-804A-0230F3E0E52B@FreeBSD.org> <201308291057.43027.jhb@freebsd.org> <8F836479-BC3A-4679-A7AA-3BCDD34AE6C5@FreeBSD.org> <52204746.2070900@freebsd.org> <ADADF693-B140-4C87-B464-9F139B31E7B5@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/30/13 00:35, David Chisnall wrote: > On 30 Aug 2013, at 08:18, Julian Elischer <julian@freebsd.org> wrote: > >> As far as I'm concerned we can even slate it for >> "possible removal in 10.2-- if clang has proven up to the task" > I would be happy to ship gcc, as long as: > > - It's explicitly marked as deprecated and due for removal at some point in the 10.x timeframe. > - libstdc++ is gone (the amount of pain it's causing ports is phenomenal). > So the real driver here is switching to libc++. Is there really no way at all to use it with gcc? If, even with hacking, we could arrange that to work then it seems that all of our problems would go away. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5220B1F3.1030807>