From owner-freebsd-arm@freebsd.org Sat May 21 01:43:54 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BC0BB43001 for ; Sat, 21 May 2016 01:43:54 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from erouter6.ore.mailhop.org (erouter6.ore.mailhop.org [54.187.213.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1ADB01663 for ; Sat, 21 May 2016 01:43:53 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 533551e0-1ef5-11e6-896e-fd5016d7ee1b X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sat, 21 May 2016 01:42:49 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u4L1hixD059381; Fri, 20 May 2016 19:43:44 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1463795024.1180.348.camel@freebsd.org> Subject: Re: upgrading arm6hf From: Ian Lepore To: bob prohaska Cc: freebsd-arm Date: Fri, 20 May 2016 19:43:44 -0600 In-Reply-To: <20160520231622.GI1049@www.zefox.net> References: <20160519232102.GF1049@www.zefox.net> <20160520021633.GG1049@www.zefox.net> <20160520065945.GH1049@www.zefox.net> <1463776364.1180.340.camel@freebsd.org> <20160520231622.GI1049@www.zefox.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2016 01:43:54 -0000 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