Re: libsigsegv self test hanging

2017-11-22 Thread Thomas Klausner
On Wed, Nov 22, 2017 at 11:52:46PM +, m...@netbsd.org wrote: > Are both with GCC 5.5 or did you try 5.4 too? I'm not sure. My best guess is 5.4 too. The problem is -- if I kill the hanging conftest executables, the libsigsegv (and then clisp) build succeeds, so I can't tell from the

Re: Custom kernel builds failing w/undeclared identifiers?

2017-11-22 Thread Robert Elz
Date:Thu, 23 Nov 2017 00:05:42 -0600 (CST) From:"John D. Baker" Message-ID: | I'll try rolling this change back and seeing if that works. I'm puzzled | by what about my configs is

Re: Custom kernel builds failing w/undeclared identifiers?

2017-11-22 Thread John D. Baker
On Thu, 23 Nov 2017, Paul Goyette wrote: > > There was a recent change to config(1) and (I think) a bump in the > > grammar version for config(5). See > > > > http://mail-index.netbsd.org/source-changes/2017/11/19/msg089808.html As this appears to deal with "ioconf", it appears to be a

Re: Custom kernel builds failing w/undeclared identifiers?

2017-11-22 Thread Paul Goyette
On Thu, 23 Nov 2017, Paul Goyette wrote: There was a recent change to config(1) and (I think) a bump in the grammar version for config(5). See http://mail-index.netbsd.org/source-changes/2017/11/19/msg089808.html And several others shortly preceeding the above, all the way back to

Re: Custom kernel builds failing w/undeclared identifiers?

2017-11-22 Thread Paul Goyette
On Wed, 22 Nov 2017, John D. Baker wrote: Following changes to -current in the last few days, some(?) of my custom kernels have been failing to build with undeclared identifiers. E.g.: on sparc: [...] --- ioconf.o --- ioconf.c:331:55: error: 'pspec5' undeclared here (not in a function) {

Custom kernel builds failing w/undeclared identifiers?

2017-11-22 Thread John D. Baker
Following changes to -current in the last few days, some(?) of my custom kernels have been failing to build with undeclared identifiers. E.g.: on sparc: [...] --- ioconf.o --- ioconf.c:331:55: error: 'pspec5' undeclared here (not in a function) { "dma", "dma_sbus", 1, STAR, loc+ 14,

Re: Automated report: NetBSD-current/i386 test failure

2017-11-22 Thread Robert Elz
Date:Thu, 23 Nov 2017 03:47:54 + (UTC) From:NetBSD Test Fixture Message-ID: <151140887413.3239.7965355474725373...@babylon5.netbsd.org> | The newly failing test cases are: | | net/if_vlan/t_vlan:vlan_vlanid |

Automated report: NetBSD-current/i386 test failure

2017-11-22 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/if_vlan/t_vlan:vlan_vlanid net/if_vlan/t_vlan:vlan_vlanid6 The above tests failed in each of the last 3 test runs, and passed in at least 27 consecutive runs before

daily CVS update output

2017-11-22 Thread NetBSD source update
Updating src tree: P src/distrib/sets/sets.subr P src/external/bsd/nvi/dist/common/delete.c P src/external/bsd/nvi/dist/common/search.c P src/external/bsd/nvi/dist/ex/ex.c P src/external/bsd/nvi/dist/vi/v_sentence.c P src/share/mk/bsd.test.mk P src/sys/arch/x86/x86/pmap.c P

Re: libsigsegv self test hanging

2017-11-22 Thread maya
Are both with GCC 5.5 or did you try 5.4 too?

libsigsegv self test hanging

2017-11-22 Thread Thomas Klausner
libsigsegv in pkgsrc hangs for me during pbulk builds in the configure step on NetBSD-8.99.7/amd64 (and 8.99.5, but it worked not too far ago): checking whether a signal handler can be left through longjmp... The message comes from the appended m4 file. I tried extracting the corresponding c

Re: netbsd 8 (beta) failing to load ixg device

2017-11-22 Thread Martin Husemann
On Wed, Nov 22, 2017 at 12:28:03PM -0500, Derrick Lobo wrote: > Hi SAITOH Masanobu > > > I sent a new pullup request: > > http://releng.netbsd.org/cgi-bin/req-8.cgi?show=361 > >It's little hard to fix that problem with small patch. I'm going to send a > >jumbo patch for ixg(4) to fix a lot

RE: netbsd 8 (beta) failing to load ixg device

2017-11-22 Thread Derrick Lobo
Hi SAITOH Masanobu > I sent a new pullup request: > http://releng.netbsd.org/cgi-bin/req-8.cgi?show=361 >It's little hard to fix that problem with small patch. I'm going to send a >jumbo patch for ixg(4) to fix a lot of bugs and it'll fix this >problemcleanly. I tried the daily Beta8

Re: panic by "acpidump -dt" on -current(Nov 22)

2017-11-22 Thread Chavdar Ivanov
ic+0x3c >>> trap() at netbsd:trap+0xbf0 >>> --- trap (number 6) --- >>> pmap_enter_ma() at netbsd:pmap_enter_ma+0xe2a >>> pmap_enter_default() at netbsd:pmap_enter_default+0x1d >>> udv