From owner-freebsd-questions@freebsd.org Fri Apr 7 04:53:55 2017 Return-Path: Delivered-To: freebsd-questions@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 124FCD3244D for ; Fri, 7 Apr 2017 04:53:55 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (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 ED33F6EE for ; Fri, 7 Apr 2017 04:53:54 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 43AB311023E; Thu, 6 Apr 2017 23:53:52 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 1C17A11023A; Thu, 6 Apr 2017 23:53:52 -0500 (CDT) Date: Thu, 6 Apr 2017 23:53:52 -0500 From: Doug McIntyre To: Carl Johnson Cc: freebsd-questions@freebsd.org Subject: Re: 12-Current for Raspberry Pi 2? Message-ID: <20170407045352.GB51176@geeks.org> References: <86wpawx4w1.fsf@elm.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86wpawx4w1.fsf@elm.localnet> User-Agent: Mutt/1.8.0 (2017-02-23) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 04:53:55 -0000 On Thu, Apr 06, 2017 at 08:39:42PM -0700, Carl Johnson wrote: > Does anybody know what has happened with the RPi2 for 12-Current? There > haven't been any snapshots at the website to try out for several weeks > now. There are snapshots for the RPi-B and the other armv6 boards. Has > somebody decided to drop it for 12.0 or something? If I follow along correctly (eg. on the freebsd-arm mailing list), binutils was updated to v2.28 in base, with a different exit code for an error condition that was silently failing before, but now totally breaks the build tree for aarch64. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218198 https://lists.freebsd.org/pipermail/freebsd-arm/2017-March/015957.html https://lists.freebsd.org/pipermail/freebsd-arm/2017-April/016017.html So, the maintainers have to fix the build tree problems.