Trimmed Mark's last reply, to provide more verbose output from the
sparc64 build that failed just now with the same error, but more
verbosity.
>>> stage 3.1: building everything
--
In file included from /usr/src/sys/sys/param.h:96,
On 2018-Aug-31, at 9:40 AM, Glen Barber wrote:
> On Fri, Aug 31, 2018 at 09:34:00AM -0700, Mark Millard wrote:
>> On Fri, Aug 31, 2018 at 02:20:09PM +, Glen Barber wrote:
On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> On 30 August 2018 at 22:46, Glen Barber wrote:
>>
On Fri, Aug 31, 2018 at 09:34:00AM -0700, Mark Millard wrote:
> On Fri, Aug 31, 2018 at 02:20:09PM +, Glen Barber wrote:
> > > On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> > > > On 30 August 2018 at 22:46, Glen Barber wrote:
> > > > >
> > > > > As I look closer at the log, I hav
On Fri, Aug 31, 2018 at 02:20:09PM +, Glen Barber wrote:
> > On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> > > On 30 August 2018 at 22:46, Glen Barber wrote:
> > > >
> > > > As I look closer at the log, I have a sneaking suspicion this may have
> > > > been a transient. I'm redo
On Fri, Aug 31, 2018 at 3:20 PM Glen Barber wrote:
>
> On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> > On 30 August 2018 at 22:46, Glen Barber wrote:
> > >
> > > As I look closer at the log, I have a sneaking suspicion this may have
> > > been a transient. I'm redoing the i386 buil
On Fri, Aug 31, 2018 at 02:20:09PM +, Glen Barber wrote:
> On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> > On 30 August 2018 at 22:46, Glen Barber wrote:
> > >
> > > As I look closer at the log, I have a sneaking suspicion this may have
> > > been a transient. I'm redoing the i3
On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
> On 30 August 2018 at 22:46, Glen Barber wrote:
> >
> > As I look closer at the log, I have a sneaking suspicion this may have
> > been a transient. I'm redoing the i386 build against the original
> > r338401 for i386 alone as a test, if
On 30 August 2018 at 22:46, Glen Barber wrote:
>
> As I look closer at the log, I have a sneaking suspicion this may have
> been a transient. I'm redoing the i386 build against the original
> r338401 for i386 alone as a test, if nothing else, to see if it fails in
> the same place.
What's the fa
On Fri, Aug 31, 2018 at 02:46:07AM +, Glen Barber wrote:
> On Fri, Aug 31, 2018 at 02:22:34AM +, Glen Barber wrote:
> > Author: gjb
> > Date: Fri Aug 31 02:22:33 2018
> > New Revision: 338404
> > URL: https://svnweb.freebsd.org/changeset/base/338404
> >
> > Log:
> > Revert r338401, as th
On Fri, Aug 31, 2018 at 02:22:34AM +, Glen Barber wrote:
> Author: gjb
> Date: Fri Aug 31 02:22:33 2018
> New Revision: 338404
> URL: https://svnweb.freebsd.org/changeset/base/338404
>
> Log:
> Revert r338401, as the i386 build is broken.
>
> Approved by:re (implicit)
> Sponso
Author: gjb
Date: Fri Aug 31 02:22:33 2018
New Revision: 338404
URL: https://svnweb.freebsd.org/changeset/base/338404
Log:
Revert r338401, as the i386 build is broken.
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation
Modified:
head/sys/conf/newvers.sh
Modified: head/sy
11 matches
Mail list logo