Date: Fri, 25 Jul 2014 23:46:08 -0700 From: Jordan Hubbard <jkh@mail.turbofuzz.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: what's the updated command(s) to build a toolchain for r-pi! Message-ID: <5E6D5D2B-5808-463F-B3D8-595030B2E285@mail.turbofuzz.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 Jul 25, 2014, at 11:37 PM, Nathan Whitehorn <nwhitehorn@freebsd.org> = wrote: > Why do you need the xdev toolchain for building world? Just make = buildworld TARGET=3Darm TARGET_ARCH=3Darmv6 will do the trick. Sorry, I was being a bit too vague there I see. I either use crochet = (or the non-crochet tools, since crochet is broken for me right now) to = create bootable .img=92s that I can then simply copy to an SD / CF card = and boot on the rpi or, as a distinct second choice, I use the rpi to = self-host its updating process by building on it. You=92re right (and = it hadn=92t really occurred to me) that I could also just do the = buildworld / buildkernel on an intel box and then mount /usr/obj and do = the installworld / installkernel on the rpi. It=92s still no = substitute for crochet in creating entire new images, but certainly = better than nothing, and I guess I could always update the image = in-place and then copy it back the other way for cloning purposes. Hmmm. Thanks for the suggestion. :) That will save me some time. - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E6D5D2B-5808-463F-B3D8-595030B2E285>