On Thu, 22 Dec 2016, John D. Baker wrote:
> D'oh! or more likely "DBG=-g" strikes again (at least on netbsd-7 hosts).
Nope. Commenting that out, cleaning out the "dtrace" objdir, and restarting
didn't change the result.
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ /
On Thu, 22 Dec 2016, John D. Baker wrote:
> .if "${MACHINE}" == "i386" || "${MACHINE}" == "amd64"
> DBG=-g
> .endif
>
> so perhaps the failure is triggered by "MKDEBUG" and/or "MKDEBUG_LIB".
D'oh! or more likely "DBG=-g" strikes again (at least on netbsd-7 hosts).
It was added as a suggestion f
Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/lib/libc/time/ctime.3
P src/libexec/fingerd/fingerd.8
P src/share/man/man9/Makefile
P src/sys/arch/acorn26/acorn26/start.c
P src/sys/arch/acorn32/acorn32/rpc_machdep.c
P src/sys/arch/acorn32/eb7500atx/eb7500atx_machdep.c
P src/sys/arch/algo
I forgot to mention MAKECONF points to a custom "mk.conf" which contains:
# mk.conf
MKDEBUG=yes
MKDEBUG_LIB=yes
USE_PIGZGZIP=yes
.if "${MACHINE}" == "i386" || "${MACHINE}" == "amd64"
DBG=-g
.endif
so perhaps the failure is triggered by "MKDEBUG" and/or "MKDEBUG_LIB".
--
|/"\ John D. Baker, KN5U
Since this commit:
http://mail-index.netbsd.org/source-changes/2016/12/21/msg080075.html
I have been unable to build releases for amd64 or i386 on hosts running
netbsd-7 or -current (7.99.51).
On a netbsd-7/amd64 host, a non-update build of amd64-current to empty
obj/DEST dirs fails with:
[..
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2016.12.22.16.05.14 cherry src/sys/arch/cesfic/cesfic/machdep.c,v 1.67
2016.12.22.16.05.15 cherry src/sys/arch/luna68k/luna68k/pmap_bootstrap.c,v
1.37
On Thu, Dec 22, 2016 at 03:34:59PM +0100, Maxime Villard wrote:
> I've deeply investigated this, and I don't see what's wrong. The issue I was
> talking about yesterday is apparently unrelated.
>
> It seems that our i386/xen code somehow does not tolerate having a pa
> allocated
> before the LDT.
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 2016.12.22.14.11.58.
An extract from the build.sh output follows:
postinstall-fix-obsolete_stand ===> .
--- post
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2016.12.22.12.39.40 abhinav src/usr.bin/finger/finger.1,v 1.19
2016.12.22.12.42.24 abhinav src/libexec/fingerd/fingerd.8,v 1.21
2016.12.22.12.55.21 c
I've deeply investigated this, and I don't see what's wrong. The issue I was
talking about yesterday is apparently unrelated.
It seems that our i386/xen code somehow does not tolerate having a pa allocated
before the LDT. In fact, it has nothing to do with lapic and all the things
I've committed;
On Thu, Dec 22, 2016 at 01:45:39PM +, NetBSD Test Fixture wrote:
> --
> ./usr/share/man/html9/uvm_hotplug.html
> ./usr/share/man/man9/uvm_hotplug.9
> = end of 2 extra files ===
> *** [checkflist] Error code 1
> nb
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 2016.12.22.11.46.48.
An extract from the build.sh output follows:
--- postinstall-fix-obsolete_stand ---
===
12 matches
Mail list logo