Date: Wed, 24 May 2017 17:16:38 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: David Wolfskill <david@catwhisker.org>, Dimitry Andric <dim@FreeBSD.org>, current@freebsd.org Subject: Re: ino64? r318606 -> r318739 OK; r318739 -> r318781 fails SIGSEGV Message-ID: <20170524141638.GP1622@kib.kiev.ua> In-Reply-To: <20170524135905.GZ1190@albert.catwhisker.org> References: <20170524121033.GL1622@kib.kiev.ua> <F75597F9-86DF-4CD5-B8B0-5169D2D96DD9@FreeBSD.org> <20170524130143.GL1190@albert.catwhisker.org> <20170524133558.GO1622@kib.kiev.ua> <20170524135905.GZ1190@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 24, 2017 at 06:59:05AM -0700, David Wolfskill wrote: > On Wed, May 24, 2017 at 04:35:58PM +0300, Konstantin Belousov wrote: > > If build of r318739 succed, can you try, please, to rebuild the current > > latest sources, but now with reverted r318750 ? > > It did complete successfully. > > I have updated /usr/src back to 318781, then started a new build. So are you building stock 318781, or did you reverted r318750 ? > > While it has not yet completed ">>> stage 4.2: building libraries", it > is well beyond the provious point of failure (again, building parts of > clang/libllvm). > > I'm reporting now, as I'll need to head in to work fairly soon. I > should be able to report definitively a bit later.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170524141638.GP1622>