From owner-freebsd-current@FreeBSD.ORG Sat Aug 24 10:30:26 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4212DB0F; Sat, 24 Aug 2013 10:30:26 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E384E2675; Sat, 24 Aug 2013 10:30:25 +0000 (UTC) Received: by mail-ve0-f179.google.com with SMTP id c13so1058861vea.24 for ; Sat, 24 Aug 2013 03:30:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NsyY9RKbDWjWGPwI3d2k/coa2u0cbHz79uH+kd0/Hi4=; b=xhon9Zr1VVXsi7ugO7FQXD2mkdE/S+Mgl0JOoijFk/PRHTrotQaDK9kSzNGony0P0O DKRWkLQusiASc1nl55fsbl7E2rgPQr+w72N1Ru/KhBTavYQLCRa+dRzy8FOQdh67XBbY 5fRTPzrls+uNWacL9ilb5g5ZcQik2n/gzkTJEcMiGU6opx0/GL2S1y1RMWY8nzYy3WYu y03BWQ0lmitW9daf+vV6JGWU6RE1SlEWm8T+RyO5ibPI6VgMZcQ7KIbrv9KgwhwAmPVb Yjpo/S0yT0eOhCQpwRveDeI9dkDHBgGbaKdCqwIT0JMIWoYicsuqIotZltvkRS3QV/bo AVVQ== MIME-Version: 1.0 X-Received: by 10.220.199.5 with SMTP id eq5mr3909053vcb.16.1377340224997; Sat, 24 Aug 2013 03:30:24 -0700 (PDT) Received: by 10.220.96.78 with HTTP; Sat, 24 Aug 2013 03:30:24 -0700 (PDT) In-Reply-To: <521745F2.8050607@passap.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> Date: Sat, 24 Aug 2013 06:30:24 -0400 Message-ID: Subject: Re: GCC withdraw From: "Sam Fourman Jr." To: Boris Samorodov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: toolchain@freebsd.org, FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2013 10:30:26 -0000 > 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; > > Well, we write rules and we brake them. ;-) > > Just say that we know we brake them but it's inevitable because... > And go futher. > I am not a developer, just a user, so I am not versed in all of the issues but I would REALLY like to see gcc moved to ports for 10.x In my opinion this just needs to happen, if ports break, we deal with that on a case by case basis. FreeBSD as a community made the decision to move to clang as a compiler, and moving gcc to ports enforces that decision, I prefer the "rip the band aid off" approach because it brings issues to light faster, and now people have real reasons to fix things. Now, I am aware that other architectures like ARM etc. need gcc in base for basic things like building kernel/world, because clang cant do this yet. Maybe this is over simplifying it a bit but can't we just modify scripts in some way to pull gcc from ports into base, for these platforms at build time? SVN *is* in base now (svnlite) >From an outside look at this, it seems to me that we're holding back the amd64 platform just because the developer activity is a little more sparse than we would prefer on other platforms. Other platforms are important and they are needed, but those platforms are the ones that need patched up, they are the ones that need the band-aids implemented so that gcc still works for them. So I vote, let's not give ourselves the burden of "lugging" dead weight in base for another 5 years. (in 2017 do we still want to be worrying about gcc in base?) So in the name of progress, let's make a comfortable final resting place for gcc in our ports tree and look to clang for our future. Thoughts, Sam Fourman Jr.