Date: Fri, 20 May 2016 19:43:44 -0600 From: Ian Lepore <ian@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: upgrading arm6hf Message-ID: <1463795024.1180.348.camel@freebsd.org> In-Reply-To: <20160520231622.GI1049@www.zefox.net> References: <CAFnjQbuH1%2Bmxid6_HdpayejNxayMHahB-JVi8=6oKNGjf9vtow@mail.gmail.com> <CANCZdfrx%2BUJdB0F9CRX=sE=2kfEBDjeLHjvADasvbUd95n56UQ@mail.gmail.com> <CAFnjQbsnEtaxRXHTvFLzWRFndUUFPyV5jW3o%2Bo=gPQxRU5bGCg@mail.gmail.com> <20160519232102.GF1049@www.zefox.net> <20160520021633.GG1049@www.zefox.net> <CANCZdfrRwnHvo1AyQxYrRQjyp9MWuNXYfX3HWub4Dc0Z%2BJ%2BFDg@mail.gmail.com> <20160520065945.GH1049@www.zefox.net> <1463776364.1180.340.camel@freebsd.org> <20160520231622.GI1049@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2016-05-20 at 16:16 -0700, bob prohaska wrote: > On Fri, May 20, 2016 at 02:32:44PM -0600, Ian Lepore wrote: > > On Thu, 2016-05-19 at 23:59 -0700, bob prohaska wrote: > > > Just did a reboot, uname -p reports > > > root@www:~ # uname -p > > > armv6hf > > > > > > > FYI, this just got fixed with Warner's r300324 commit. I think > > only > > your kernel needs rebuilding to make it right in userland too. > > > > -- Ian > > > Indeed, the kernel build completed with no special options, the > install > required DESTIR=/ but that's all. Will the DESTDIR requirement > persist? > > After reboot the system says it's at r300334M, uname -p reports > armv6, > not armv6hf as before; is this expected? World and userland are now > very slightly out of sync, so the next step is to update and repeat > a complete OS build/install cycle. A few minutes into the process all > seems well. > > Thank you very much! > > bob prohaska I'm not seeing any such problems, I can do a "make installkernel KERNCONF=IMX6" without any destdir, and it works fine. I've also got a buildworld running on the wandboard right now without any problems (but it will be a few hours to finish). Oh wait... but your system *was* armv6hf, right? I think you've got a compiler and other tools that think the native arch is armv6hf, but now with your updated kernel any tool that asks for sysctl hw.machine_arch or uname -p will be told "armv6", mismatching the tools (even make itself has a notion of the native arch, expressed in the MACHINE_ARCH make variable). This trouble didn'e didn't happen to me because my initial build and install after the armv6hf->armv6 change were done as crossbuilds on an amd64 machine. I'm not sure what the proper update-in-place mechanism is for this (and have even less idea right now how to get your current frankensystem sane again). -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1463795024.1180.348.camel>