Date: Fri, 25 Jul 2014 23:48:04 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: what's the updated command(s) to build a toolchain for r-pi! Message-ID: <CAJ-VmomLGG8eS=LpeyXuOmVMVR0PQDmXmP8a_K%2BV4Yy-cbyScA@mail.gmail.com> In-Reply-To: <53D34CA8.4040009@freebsd.org> References: <CAJ-Vmo=qm6_e%2BHamddxuuMj6n1UBjM1EThTigb3W5FJrvxjnSw@mail.gmail.com> <538542CC-D053-4904-AE6F-0C76D946F971@mail.turbofuzz.com> <53D34CA8.4040009@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 July 2014 23:37, Nathan Whitehorn <nwhitehorn@freebsd.org> wrote: > > On 07/25/14 23:24, Jordan Hubbard wrote: >> >> On Jul 25, 2014, at 11:16 PM, Adrian Chadd <adrian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomLGG8eS=LpeyXuOmVMVR0PQDmXmP8a_K%2BV4Yy-cbyScA>