From owner-freebsd-current@freebsd.org  Mon Mar 12 02:37:20 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D9A9F40808
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 12 Mar 2018 02:37:20 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id B40CA8A8FA
 for <freebsd-current@freebsd.org>; Mon, 12 Mar 2018 02:37:19 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 71B66F40803; Mon, 12 Mar 2018 02:37:19 +0000 (UTC)
Delivered-To: current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FA93F40802
 for <current@mailman.ysv.freebsd.org>; Mon, 12 Mar 2018 02:37:19 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.soaustin.net",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E9C588A8F4
 for <current@freebsd.org>; Mon, 12 Mar 2018 02:37:18 +0000 (UTC)
 (envelope-from linimon@lonesome.com)
Received: from lonesome.com (bones.soaustin.net [192.108.105.22])
 by mail.soaustin.net (Postfix) with ESMTPSA id 80B763AA;
 Sun, 11 Mar 2018 21:37:15 -0500 (CDT)
Date: Sun, 11 Mar 2018 21:37:14 -0500
From: Mark Linimon <linimon@lonesome.com>
To: Ian FREISLICH <ian.freislich@capeaugusta.com>
Cc: current <current@freebsd.org>
Subject: Re: Clang-6 and GNUisms.
Message-ID: <20180312023714.GA781@lonesome.com>
References: <4ea06b48-d451-f2b3-4c20-4963f829333b@capeaugusta.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4ea06b48-d451-f2b3-4c20-4963f829333b@capeaugusta.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 02:37:20 -0000

The problem is even worse on armv6/armv7/aarch64, and much worse on
powerpc64/sparc64, which still have gcc in base.

I have not been saving up the emails where ports committers have been
fixing various failure modes.  I hesitate to start making harmless-
seeming patches myself for fear of my non-existant C++ skills.

I would be glad to help someone write up some documentation.  This
affects hundreds of port builds right now -- I have not even caught
up yet on tracking them all.

mcl