Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/public-domain/tz/dist/NEWS
U src/external/public-domain/tz/dist/TZDATA_VERSION
P src/external/public-domain/tz/dist/africa
P src/external/public-domain/tz/dist/europe
P
On Sunday 2018-10-28 13:16 +1100, Geoff Wing output:
:Hi,
:I'm running the same -current build on two x64 machines. One is a VM
:and the other is bare-metal. I'm rebuilding in case something funny
:happened in the build and noone else can reproduce anything similar.
:
:The ntpdate in
On Sunday 2018-10-28 08:32 +0700, Robert Elz output:
:I don't suppose that your ToD clock is 6 seconds incorrect, and
:ntpdate run from /etc/rc is fixing that (but the ToD clock isn't being
:updated) ?
:
:if it is not that, then you're right, something weird is happening.
Hi,
I'm running the same
Date:Sun, 28 Oct 2018 12:01:55 +1100
From:Geoff Wing
Message-ID: <20181028010155.ga1...@primenet.com.au>
| Ah, I just rebooted it so that's 1 min and 13 seconds,
| not 1 month and 13 seconds.
I should have known that, since I'm responsible for the current code
On Sunday 2018-10-28 07:19 +0700, Robert Elz output:
: | The dmesg time matches what appears in kern.boottime but I don't see a 5-6
: | second step in rc.log when ntpdate is run.
:You wouldn't now. The system from which you showed that output has
:been up for a month. During that month,
Date:Sun, 28 Oct 2018 09:51:43 +1100
From:Geoff Wing
Message-ID: <20181027225143.ga...@primenet.com.au>
| The dmesg time matches what appears in kern.boottime but I don't see a 5-6
| second step in rc.log when ntpdate is run.
You wouldn't now. The system from
On Saturday 2018-10-27 19:03 +0700, Robert Elz output:
:Date:Sat, 27 Oct 2018 17:39:16 +1100
:From:Geoff Wing
:Message-ID: <20181027063916.ga2...@primenet.com.au>
:
: | dates output by "dmesg -T" are not matching real time. Using a program
: | to generate a
Hello Greg, Andreas and Riccardo,
Leonardo Taccari writes:
> [...]
> I have just added it to buildlink3.mk, please let me know if that
> fixes the problem you have reported! (just a `make replace' in
> emacs or any other problematic package should be enough to test
> that)
> [...]
(More
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2018.10.27.11.39.12 skrll src/usr.bin/gzip/gzip.c,v 1.116
2018.10.27.11.52.26 kre src/usr.bin/gzip/unlz.c,v 1.2
Log files can be found at:
On Oct 27, 12:59pm, g...@gson.org (Andreas Gustafsson) wrote:
-- Subject: Re: Automated report: NetBSD-current/i386 build failure
| The i386 build is still failing in gzip:
|
| /tmp/bracket/build/2018.10.27.07.24.58-i386/src/usr.bin/gzip/unlz.c:580:21:
error: format '%td' expects argument of
Hello Andreas, Greg and Riccardo,
Andreas Gustafsson writes:
> Greg, Riccardo,
>
> Please disregard the parts of my earlier mail that pertained to
> tests run under NetBSD-current. I had missed the fact that
> ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz is only
> regenerated weekly,
Date:Sat, 27 Oct 2018 17:39:16 +1100
From:Geoff Wing
Message-ID: <20181027063916.ga2...@primenet.com.au>
| dates output by "dmesg -T" are not matching real time. Using a program
| to generate a segfault dmesg is showing times in the future:
dmesg times come
The i386 build is still failing in gzip:
/tmp/bracket/build/2018.10.27.07.24.58-i386/src/usr.bin/gzip/unlz.c:580:21:
error: format '%td' expects argument of type 'ptrdiff_t', but argument 3 has
type '__off_t {aka long long int}' [-Werror=format=]
--
Andreas Gustafsson, g...@gson.org
Greg, Riccardo,
Please disregard the parts of my earlier mail that pertained to
tests run under NetBSD-current. I had missed the fact that
ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz is only
regenerated weekly, and accidentally tested using a pkgsrc.tar.gz
that was five days old and
Hi,
dates output by "dmesg -T" are not matching real time. Using a program
to generate a segfault dmesg is showing times in the future:
# sysctl -w kern.logsigexit=1
kern.logsigexit: 0 -> 1
# ./segfault; date
[1]18445 segmentation fault ./segfault
Sat Oct 27 17:33:56 AEDT 2018
# dmesg -T |
15 matches
Mail list logo