Date: Fri, 8 Aug 2014 09:35:55 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: What platform do you use? Message-ID: <724D10EE-F6DF-4366-91CF-AE4419847389@gromit.dlib.vt.edu> In-Reply-To: <24403276-D738-4CB1-A3BE-BBB72D4370C6@bsdimp.com> References: <7EC2AB25-5949-40BF-A5AA-BF4C98F3F640@bsdimp.com> <20140805182438.GP88623@funkthat.com> <53E3E2C7.9000802@hot.ee> <24403276-D738-4CB1-A3BE-BBB72D4370C6@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 7, 2014, at 5:34 PM, Warner Losh <imp@bsdimp.com> wrote: >=20 > On Aug 7, 2014, at 2:34 PM, Sulev-Madis Silber (ketas) = <madis555@hot.ee> wrote: >=20 >> On 2014-08-05 21:24, John-Mark Gurney wrote: >>> I also have a BBW that I occasionally test w/ but since I haven't = got >>> it netbooting, the cost of building an entire image and writing it = to >>> SLOW microsd prevents me from testing as much... >>=20 >> I wonder why people like to update their embedded systems by taking = card >> out, completely overwriting it with new data and putting card back = in. >> No wonder that it's slow, complex & heedlessly wears out your flash. >>=20 >> If I do this in my BBB I would get myself pissed very soon because of >> the effort required. I never bothered to netboot too, because I = wanted >> to test it in insecure network conditions. >> I mean, I don't remember a case where I needed to take HDD to another >> machine for upgrade. The issue where it's not practical to compile >> something locally is completely unrelated with this, too. >=20 > make installworld works too, as does extracting the binary sets. The = new installer > should work, but I=92ve not tried it. It would be handy for those of us wanting to cross-build FreeBSD/arm=20 for someone who is familiar with the build process to give a quick=20 example of how to update a FreeBSD/arm installation that is cross-built=20= on another system. In the past, I've had the impression that the build=20= infrastructure on the target system sometimes needs to be in alignment=20= with the new kernel/world you're trying to install, and so NFS-mounting=20= /usr/src and /usr/obj or copying it to the target system fails to yield=20= a successful "make installworld" on the target system. Maybe this is=20 no longer the case, as I believe great strides have been made in the=20 realm of cross-building. Up to now, I have largely used Crochet to build images for my R-PI and=20= BBB. That's okay for initial install, but I'm much more familiar with=20= updating from source and would like to do that from then on. In the=20 past, FreeBSD/arm has been too flaky for me to do a native build (I've=20= posted here about that in the past), but, besides that, it would be=20 nice to cut down the long native build times by cross-building on a=20 much faster system. I have an R-PI and BBB and would like to cross-build (for update=20 purposes) on my FreeBSD/amd64 10-STABLE system. Could you post a known=20= way to do this? I can NFS-mount from the FreeBSD/amd64 or else have it=20= put /usr/src and /usr/obj on an USB external hard drive that I can then=20= connect to my R-PI or BBB for updating. Either is okay with me. Thanks in advance. Cheers, Paul. PS: What is the make target to build the binary sets? Does this work=20 when cross-building?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?724D10EE-F6DF-4366-91CF-AE4419847389>