Date: Sun, 22 May 2016 16:04:55 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Ian Lepore <ian@freebsd.org> Cc: Ulrich Grey <usenet@ulrich-grey.de>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: upgrading arm6hf Message-ID: <20160522230455.GA48692@www.zefox.net> In-Reply-To: <1463953014.1180.395.camel@freebsd.org> References: <20160520231622.GI1049@www.zefox.net> <20160521002859.GJ1049@www.zefox.net> <1463795214.1180.351.camel@freebsd.org> <20160521021227.GK1049@www.zefox.net> <1463797063.1180.354.camel@freebsd.org> <20160521023515.GA15151@bluezbox.com> <20160521155043.GM1049@www.zefox.net> <1463849864.1180.364.camel@freebsd.org> <20160521184422.GN1049@www.zefox.net> <1463953014.1180.395.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ian, On Sun, May 22, 2016 at 03:36:54PM -0600, Ian Lepore wrote: > > I tracked this down today and just committed the fix as r300438. The > problem was that MACHINE_CPUARCH was being set to 'armhf' instead of > 'arm' because the translation for 'hf' suffix was removed from > share/sys.mk. We'll need to leave that translation in place for a few > months until everyone running self-hosted armv6hf systems have had a > chance to update. > > So now the build with TARGET_ARCH=armv6 should work. There is probably > some subset of what's in obj/ that could be deleted to avoid a full > rebuild, but I don't know what it is for sure, I just deleted > everything and started over. My build is not done yet, but it has > gotten further than it did last night, so this fix is looking good so > far. I've emptied /usr/obj and the build seems to be running. Holding my breath....8-) What's the likely scenario for upgrading pre-hf systems to post-hf? bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160522230455.GA48692>