Re: Build failure on amd64 - NACPICA related?

Yes, I did that, and as soon as my test build completed (successfully) I committed it! Thanks for doing all the hard work - my part was easy! On Mon, 12 Dec 2016, Martin Husemann wrote: On Mon, Dec 12, 2016 at 08:38:39AM +0800, Paul Goyette wrote:

Re: Build failure on amd64 - NACPICA related?

On Mon, Dec 12, 2016 at 08:38:39AM +0800, Paul Goyette wrote: > /build/netbsd-local/src/sys/arch/amd64/amd64/machdep.c:1643:17: error: > 'local_apic_va' undeclared (first use in this function) > pmap_kenter_pa(local_apic_va, local_apic_pa, > ^ >

daily CVS update output

Updating src tree: P src/doc/CHANGES P src/lib/libcurses/copywin.c P src/lib/libedit/read.c P src/libexec/httpd/bozohttpd.8 P src/libexec/httpd/bozohttpd.c P src/libexec/identd/Makefile P src/share/mk/bsd.own.mk P src/sys/arch/amd64/amd64/machdep.c P src/sys/arch/i386/i386/machdep.c P

Automated report: NetBSD-current/i386 build success

The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2016.12.11.22.38.50 martin src/sys/arch/i386/i386/machdep.c,v 1.766 Log files can be found at:

Build failure on amd64 - NACPICA related?

With up-to-date sources I'm getting # compile INSTALL_XEN3_DOMU/machdep.o /build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-gcc -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -mno-avx -msoft-float -mno-fp-ret-in-387 -ffreestanding -fno-zero-initialized-in-bss -g -O2

Re: strange observations on network configuration (ifconfig)

Hi, Thank you for the investigation. On Sun, Dec 11, 2016 at 9:08 PM, Frank Kardel wrote: > Hi ! > > Reverting that change (1.24->1.25) and using RTF_LLDATA instead of > RTF_LLINFO seems to solve the problem. > Is this correct or am I overlooking something? Local routes

Re: xorg.conf is read but not acted on correctly

On Saturday 10 December 2016 22:51:32 Soren Jacobsen wrote: > On 12/10 16:53, Dave Tyson wrote: > > [ 2175.541] Build Operating System: NetBSD/amd64 - > > [...] > > [ 2175.542] (WW) The directory "/usr/X11R7/share/fonts/X11/TTF" does > > not exist. > > Update your trees (both src and xsrc) and

Re: xorg.conf is read but not acted on correctly

co...@sdf.org writes: > Try this: Cool! I've got a working console again. Thanks! :) -tih -- I like long walks, especially when they are taken by people who annoy me.

Re: strange observations on network configuration (ifconfig)

Hi ! Reverting that change (1.24->1.25) and using RTF_LLDATA instead of RTF_LLINFO seems to solve the problem. Is this correct or am I overlooking something? Frank On 12/11/16 11:38, Frank Kardel wrote: Hi, thanks for your reply. As for backward compatibility: An old userland routed

Re: strange observations on network configuration (ifconfig)

Hi, thanks for your reply. As for backward compatibility: An old userland routed works ok with a new kernel. The log for an added interface for routed for 7.99.16 on a 7.99.42 kernel is: -- 10:38:43 -- Recv RIPv2 RESPONSE from 10.200.1.1.520 via wm1 0.0.0.0metric=9

Automated report: NetBSD-current/i386 build failure

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.11.08.40.10. An extract from the build.sh output follows: #create LEGACY/sys_select.d

Automated report: NetBSD-current/i386 build success

The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2016.12.11.06.30.11 christos src/sys/dev/files.audio,v 1.7 2016.12.11.06.37.49 christos src/share/mk/bsd.own.mk,v 1.999 Log files can be found at:

Re: strange observations on network configuration (ifconfig)

Hi, Thank you for the report. On Mon, Dec 5, 2016 at 11:47 PM, Frank Kardel wrote: > Hi ! > > when trying out a -current from 20161127 (7.99.42) I see issues with routed. > > On configuration of an interface address A.B.C.D/m the local network address > A.B.C.D is correctly