From owner-freebsd-toolchain@freebsd.org  Sun Dec 25 14:53:57 2016
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 9D31AC90F5A
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Sun, 25 Dec 2016 14:53:57 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 8C0CA1239
 for <freebsd-toolchain@FreeBSD.org>; Sun, 25 Dec 2016 14:53:57 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBPErvRK097802
 for <freebsd-toolchain@FreeBSD.org>; Sun, 25 Dec 2016 14:53:57 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 214863] lang/gcc + libc++ may fail due to spurious
 __cxa_throw_bad_array_new_length reference
Date: Sun, 25 Dec 2016 14:53:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: antoine@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback? merge-quarterly?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-214863-29464-hatZJYLXZP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
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: Sun, 25 Dec 2016 14:53:57 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214863

--- Comment #12 from Antoine Brodin <antoine@FreeBSD.org> ---
(In reply to Jan Beich (mail not working) from comment #11)
Unless the FreeBSD Security Officer changes his mind,  at 23:59 UTC December
31, 2016, FreeBSD 9.3, 10.1 and 10.2 will reach end-of-life and will no lon=
ger
be supported.

So 2017Q1 will not support those releases (unless so@ changes his mind).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=