From owner-freebsd-toolchain@freebsd.org  Mon Jul  3 13:28:14 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C4B39E6CC2;
 Mon,  3 Jul 2017 13:28:14 +0000 (UTC)
 (envelope-from gerald@pfeifer.com)
Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 07FC67022D;
 Mon,  3 Jul 2017 13:28:13 +0000 (UTC)
 (envelope-from gerald@pfeifer.com)
Received: from ainaz.pair.com (localhost [127.0.0.1])
 by ainaz.pair.com (Postfix) with ESMTP id 34E5B3F599;
 Mon,  3 Jul 2017 09:28:06 -0400 (EDT)
Received: from [192.168.1.114] (unknown [202.188.138.130])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ainaz.pair.com (Postfix) with ESMTPSA id 23ECF3F590;
 Mon,  3 Jul 2017 09:27:53 -0400 (EDT)
Date: Mon, 03 Jul 2017 21:27:31 +0800
User-Agent: K-9 Mail for Android
In-Reply-To: <1BFFF3BD-7658-452F-9369-7C2AED479FB6@dsl-only.net>
References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net>
 <BD68F3F3-A81C-4830-9169-6188A05EF6B2@dsl-only.net>
 <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com>
 <F9DACFDB-AF70-461E-B6B2-D5E9385F6D9A@dsl-only.net>
 <C25E8566-89FC-4CCE-A7AF-F8B18EB758D7@pfeifer.com>
 <E8B2DB17-7397-4BB7-95D1-76F2BFDB5278@dsl-only.net>
 <B1FFF990-9DEA-48B8-B383-477837390C3B@pfeifer.com>
 <8F50FB7C-498C-453E-AE5A-EADC60758730@dsl-only.net>
 <A4A02703-AA21-4006-AEFE-F1453B35FBCC@dsl-only.net>
 <1BFFF3BD-7658-452F-9369-7C2AED479FB6@dsl-only.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: It looks like USE_GCC=any is broken and leads to system-clang use
To: Mark Millard <markmi@dsl-only.net>
CC: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>,
 FreeBSD Ports <freebsd-ports@freebsd.org>
From: Gerald Pfeifer <gerald@pfeifer.com>
Message-ID: <A0793751-55F7-47AA-A205-396EB2F55FF4@pfeifer.com>
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 13:28:14 -0000



Am 3=2E Juli 2017 13:30:13 GMT+08:00 schrieb Mark Millard <markmi@dsl-only=
=2Enet>:
>[More on the behavior: it is more complicated than
>previously shown=2E]

It's actually pretty simple (I think)=2E Mk/bsd=2Egcc=2Emk only uses lang/=
gcc* ports that represent releases, not lang/gcc*-devel that represent snap=
shots=2E

So your patch is out of spec=2E

(I have had lang/gcc7 essentially ready for weeks, alas on a system that i=
s a dead brick due to loss of its power brick and me traveling=2E Should be=
 finally addressed by the end of this week=2E)

Gerald