From owner-freebsd-arm@FreeBSD.ORG Sat Jul 26 06:24:44 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A102462; Sat, 26 Jul 2014 06:24:44 +0000 (UTC) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 651352AEF; Sat, 26 Jul 2014 06:24:43 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 037A378AB7; Fri, 25 Jul 2014 23:24:43 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 24091-09; Fri, 25 Jul 2014 23:24:42 -0700 (PDT) Received: from [10.8.0.10] (unknown [10.8.0.10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 921D778AB2; Fri, 25 Jul 2014 23:24:41 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: what's the updated command(s) to build a toolchain for r-pi! From: Jordan Hubbard In-Reply-To: Date: Fri, 25 Jul 2014 23:24:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <538542CC-D053-4904-AE6F-0C76D946F971@mail.turbofuzz.com> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2014 06:24:44 -0000 On Jul 25, 2014, at 11:16 PM, Adrian Chadd wrote: > So, assuming I'm starting from scratch (and just assume I'm doing it > in a jail, so there's no existing toolchain to interfere) - what's the > correct way to build the cross-dev toolchain so it'll work for > crochet? I was going to ask that too. On -current, the crochet instructions = don=92t actually work since the GCC xdev build blows up. Conversely, = the clang xdev build works, but then crochet can=92t find the compiler = it=92s looking for and it blows up there. I=92m reduced to building = world on the RPI itself. 22 hours and counting. ;-) - Jordan