The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2018.07.13.01.00.17 kre src/lib/csu/common/crt0-common.c,v 1.19
Log files can be found at:
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 2018.07.12.21.42.53.
An extract from the build.sh output follows:
*where += (Elf_Addr)relocbase;
Updating src tree:
P src/crypto/external/bsd/heimdal/lib/libkadm5srv/Makefile
P src/distrib/sets/lists/base/ad.arm
P src/distrib/sets/lists/comp/ad.aarch64
P src/distrib/sets/lists/comp/ad.arm
P src/distrib/sets/lists/comp/ad.arm.shl
P src/distrib/sets/lists/comp/ad.hppa
P
On Thu, 12 Jul 2018, m...@netbsd.org wrote:
On Thu, Jul 12, 2018 at 09:32:47AM +0800, Paul Goyette wrote:
While we're on the subject of viadrm, I noticed that it was removed from the
amd64 GENERIC and ALL configs.
Since one of the premises of removal was that viadrmums was a suitable
In article <20180711190338.ga15...@dropje.13thmonkey.org>,
Reinoud Zandijk wrote:
>-=-=-=-=-=-
>
>Dear folks,
>
>in my attempt to clean up make(1) I stumbled on the following duplicate code.
>It was replaced by the cached_stat() addition but the old code was not
>removed.
Yes, because the code
Hi,
The following probably won't be of much use, but perhaps is worth
mentioning.
I have an HP laptop with a main nvme disk running Windows 10 and
VirtualBox. There is also a GPT-partitioned second 750GB disk, holding some
data plus several EFI-booting systems, one of which is NetBSD-current. I
