From owner-freebsd-toolchain@freebsd.org  Thu Feb  9 19:49:00 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 6B9B5CD8516
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Thu,  9 Feb 2017 19:49:00 +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 5B2B3B96
 for <freebsd-toolchain@FreeBSD.org>; Thu,  9 Feb 2017 19:49:00 +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 v19Jmxrg010418
 for <freebsd-toolchain@FreeBSD.org>; Thu, 9 Feb 2017 19:49:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 216707] exp-run: Update lang/gcc from GCC 4.9 to GCC 5
Date: Thu, 09 Feb 2017 19:48:59 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Flags: exp-run?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-216707-29464-w21dJuX8Sl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216707-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-216707-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: Thu, 09 Feb 2017 19:49:00 -0000

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

--- Comment #29 from John Marino <marino@FreeBSD.org> ---
It's probably out of scope, but shells/ksh93 doesn't build with gcc5 either=
.=20
Since USE_GCC isn't set for this port, nobody sees it.

We see this error if gcc5 is used:
mamake: *** exit code 1 making lib/libast

So it fails to build libast which results in a linking failure much later.

Basically FYI - in theory ports gcc should be able to build most ports but I
can understand if nobody wants to investigate further.

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