Date: Sun, 29 Sep 2019 09:46:54 -0700 From: John Kennedy <warlock@phouka.net> To: Brian Bostwick <bostwick.brian@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: Building world and kernel on RPI3 B+ compilation failure, unwind-dw2.c. Message-ID: <20190929164654.GB77308@phouka1.phouka.net> In-Reply-To: <CAM9he-XnPTbK_aGPzWbaZx_N6%2B-x9CUck4Nz0zvuOSYgukLX0A@mail.gmail.com> References: <CAM9he-Woj3gkiGPb%2BWTOq7y8kcRjG2RjPBLsXYhk-QayZx75HA@mail.gmail.com> <20190929141211.GA96467@phouka1.phouka.net> <CAM9he-XnPTbK_aGPzWbaZx_N6%2B-x9CUck4Nz0zvuOSYgukLX0A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 29, 2019 at 10:58:12AM -0400, Brian Bostwick wrote: > I ran the following to get to the revision I am at: > > *svnlite checkout https://svn.freebsd.org/base/ > <https://svn.freebsd.org/base/>releng/12.1 /usr/src* > > I then did a *snvlite update /usr/src before I got started today.* Well, It's a RPI3B+, so I'll let you know in ~28-31 hours, give or take what point in the compile that fragment lands in. That "revision" number is what I typically see tagged on the kernel number, 352780 below but 352868 in your example. I haven't caught them going down, but if that is some MFC number that isn't guaranteed to be an increasing integer, maybe it could be off. And sometimes svn and git aren't in sync (git logging behind, sometimes for extended periods of time), but this is what I'm crunching now: [git branch] master * releng/12.1 [git log (most recent-for-me entry)] commit b78e5b46c44c8db8094f7a218ba1de5cd2f5e8aa Author: gjb <gjb@FreeBSD.org> Date: Fri Sep 27 00:00:21 2019 +0000 Update releng/12.1 to BETA2 as part of the 12.1-RELEASE cycle. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) Notes: svn path=/releng/12.1/; revision=352780
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190929164654.GB77308>