From owner-freebsd-arm@FreeBSD.ORG Sat Jul 26 06:48:05 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 D136AB57; Sat, 26 Jul 2014 06:48:05 +0000 (UTC) Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81BC02C6E; Sat, 26 Jul 2014 06:48:05 +0000 (UTC) Received: by mail-qa0-f51.google.com with SMTP id k15so5481631qaq.24 for ; Fri, 25 Jul 2014 23:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=WfA9cAOQ77qE3ii6GoYktT2PwaJp2BRPOohfZEUBmio=; b=hyhkHtiCGkHhXoWwqaLlpIhS9524n9RINnbIMUBLEWiOfdH22FtPDLFGK8BVIuuw7q jy2/xkx51VR1ND5nMoZBY+TqUlzqcadlzW61gKDgio2eHzyCt5Ts/oJt+prvwRR4OuOB RqF780NjpMkbjvYce7DvXM8/0soo0CcJYweRGyEHQWlUJ5VbiizBoAkM5LSP1PbfSHqd MxmeShRCd0bc7VrHxRlxgX1gb3xQ8hRkIh6DleNbofb2ovYjiFiqnBJBdntrTFv/j8tW 5eCoQgddmoLcXxPlBPLtbpc4bm+LX0aFdGcgcESUn4SUbdkdLuUxr9b4QNhE+3iKxa4/ /jaA== MIME-Version: 1.0 X-Received: by 10.140.107.4 with SMTP id g4mr21771684qgf.100.1406357284609; Fri, 25 Jul 2014 23:48:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.1.6 with HTTP; Fri, 25 Jul 2014 23:48:04 -0700 (PDT) In-Reply-To: <53D34CA8.4040009@freebsd.org> References: <538542CC-D053-4904-AE6F-0C76D946F971@mail.turbofuzz.com> <53D34CA8.4040009@freebsd.org> Date: Fri, 25 Jul 2014 23:48:04 -0700 X-Google-Sender-Auth: _ndrJQaHyf9Vlxu9IafP-ecDrHc Message-ID: Subject: Re: what's the updated command(s) to build a toolchain for r-pi! From: Adrian Chadd To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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:48:05 -0000 On 25 July 2014 23:37, Nathan Whitehorn wrote: > > On 07/25/14 23:24, Jordan Hubbard wrote: >> >> 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= =E2=80=99t >> actually work since the GCC xdev build blows up. Conversely, the clang = xdev >> build works, but then crochet can=E2=80=99t find the compiler it=E2=80= =99s looking for and >> it blows up there. I=E2=80=99m reduced to building world on the RPI its= elf. 22 >> hours and counting. ;-) >> >> - Jordan >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > > Why do you need the xdev toolchain for building world? Just make buildwor= ld > TARGET=3Darm TARGET_ARCH=3Darmv6 will do the trick. > -Nathan because we're using crochet, so we don't have to build: * uboot * the right filesystem layout to figure out how to get the boot pieces to be recognised; * put the right boot pieces in the right spot so the pi bootloader picks it= up; * get the right combination of things to generate a useful filesystem image= . So that's why your instructions by themselves aren't enough. -a