upgrading arm6hf

[David Cornejo]

After several attempts to get past the relocation truncation errors, I
finally broke down, cross compiled on an Intel box, installed world
and kernel to an empty directory, tar'ed it all up and copied over my
RPI 2. Had full expectation I was going to kill it, but the armv6
binaries ran ok on the armv6hf kernel. I'm now going to compile a new
world and kernel on the RPI 2 and see what happens. (probably moot
since it appears that problem has since been corrected)

On Sun, May 22, 2016 at 1:04 PM, bob prohaska <fbsd at www.zefox.net> wrote:
> 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
>
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"