Kamil Rytarowski wrote:
>>> port-sparc/53277: Many ubsan tests fail on sparc
[...]
> Please recheck sparc and sparc64 with:
>
> src/external/gpl3/gcc/dist/libsanitizer/sanitizer_common/sanitizer_linux.cc
> r.1.30
I have now rechecked sparc (only, since the tests never failed on
sparc64), and the
On Mon, 15 Apr 2019, John D. Baker wrote:
> Since I have systems that reported UAR resources at ACPI, my habit has
> been to enable the "com* at acpi?" attachment and disable the "comN at isa?"
> attachments.
>
> I reverted these in my custom kernel config and my serial ports work
> normally agai
On Sun, 28 Apr 2019, John D. Baker wrote:
> I've been through a couple of update cycles on current and installed
> the latest kernel and sets. Now "com0 at isa?" in my custom kernel
> doesn't work either.
False alarm. Three-wire serial using 4-wire modular phone cord through
a butt-connector. O
On Fri, Apr 26, 2019 at 12:02:05AM +0200, Thomas Klausner wrote:
[...]
> Why are not all the fonts available for loading with wsfontload (i.e.,
> installed into /usr/share/wscons/fonts)?
Good question. At this moment there are following mapping between
loadable and built-in font files:
loadable
Hi,
after a long build time I see
end of 37 extra files
*** Failed target: checkflist
I did build using "./build.sh -U -x distribution" so it was not an
update build.
What can I do? just delete the files? if there is a command to get this
list I can try...
Riccardo
On Sun, 28 Apr 2019, Riccardo Mottola wrote:
Hi,
after a long build time I see
end of 37 extra files
*** Failed target: checkflist
I did build using "./build.sh -U -x distribution" so it was not an update
build.
What can I do? just delete the files? if there is a command to get
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
lib/libutil/t_snprintb:snprintb
The above test failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The following commits were made
Date:Sun, 28 Apr 2019 21:50:45 + (UTC)
From:NetBSD Test Fixture
Message-ID: <155648824563.27186.9065778287415893...@babylon5.netbsd.org>
| The newly failing test case is:
|
| lib/libutil/t_snprintb:snprintb
I know what is happening with that, and I will
Date:Mon, 29 Apr 2019 08:58:43 +0700
From:Robert Elz
Message-ID: <17972.1556503...@jinx.noi.kre.to>
| I know what is happening with that, and I will fix...
|
| The problem relates to a difference of opinion/misunderstanding
| of the 'F' (new style) format oper
Updating src tree:
P src/crypto/external/bsd/openssh/dist/monitor.h
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/gpl2/xcvs/dist/doc/cvs.1
P src/external/gpl2/xcvs/dist/doc/cvs.texinfo
P src/lib/libm/man/nextafter.3
P src/lib/libnvmm/Makefile
P src/lib/libnvmm/libnvmm.c
P src/lib/libnvmm/li
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2019.04.29.01.18.58.
An extract from the build.sh output follows:
--- dependall-external ---
--- aslcompilerpars
Date:Mon, 29 Apr 2019 09:33:59 +0700
From:Robert Elz
Message-ID: <22739.1556505...@jinx.noi.kre.to>
| Upon reflection, I'm inclined to instead [...]
And upon further reflection, and noticing this sentence in
the snprintb() man page (snprintb.3)
Finally, ea
Thanks!
christos
> On Apr 28, 2019, at 10:33 PM, Robert Elz wrote:
>
>Date:Mon, 29 Apr 2019 08:58:43 +0700
>From:Robert Elz
>Message-ID: <17972.1556503...@jinx.noi.kre.to>
>
> | I know what is happening with that, and I will fix...
> |
> | The problem relates t
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.04.29.02.49.35 dogcow src/usr.sbin/acpitools/acpidump/acpi.c,v 1.45
Log files can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-20
14 matches
Mail list logo