From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 11:54:20 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5F1DF5CE; Fri, 23 Aug 2013 11:54:20 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE70D214B; Fri, 23 Aug 2013 11:54:19 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [193.68.6.1]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.6/8.14.6) with ESMTP id r7NBrr9I011536 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 14:53:54 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <52174D51.2050601@digsys.bg> Date: Fri, 23 Aug 2013 14:53:53 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: GCC withdraw References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> In-Reply-To: <20130823111647.GT2951@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: toolchain@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 11:54:20 -0000 On 23.08.13 14:16, Kurt Jaeger wrote: > Hi! > >>> I have a patch that I intend to commit before the 10.0 code >>> slush that removes GCC and libstdc++ from the default build on >>> platforms where clang is the system compiler. We definitely don't >>> want to be supporting our 6-year-old versions of these for the >>> lifetime of the 10.x branch. >> Isn't it a POLA violation? >> >> As for me I expect something like this: >> . 9.x gcc default and clang in base; >> . 10.x clang default and gcc in base; >> . 11.x gcc withdraw. > If the 150 ports that only work with gcc, all work with a ports > gcc and do not need the gcc from base, would the following be OK ? > > - 9.x gcc default and clang in base; > - 10.x clang default and gcc in ports; > I believe this is the best idea so far. As long as these ports work with gcc in ports, that is. For many of the "important" ports, they do get used together with other ports that already require newer gcc from ports anyway. So no additional pollution will be created. Daniel