Re: Mesa update

2019-04-06 Thread Rin Okuyama
This is because Makefile didn't handle objdir correctly. Should be fixed now. Thanks, rin On 2019/04/06 22:42, Patrick Welche wrote: On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green wrote: thanks for the original work and fixing this i386 thing! If you would like to do an update

Re: NetBSD-current/sparc build failure

2019-04-06 Thread Andreas Gustafsson
Jason Thorpe wrote: > Fix committed. Confirmed fixed, thanks. -- Andreas Gustafsson, g...@gson.org

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

2019-04-06 Thread Andreas Gustafsson
m...@netbsd.org wrote: > That's the ALL kernel, right? we shouldn't build COMPAT_FREEBSD on any > kernel in use. The test is just doing a "build.sh release"; I don't know what kernels are included in that, I just expect it to build. -- Andreas Gustafsson, g...@gson.org

Re: Mesa update

2019-04-06 Thread Chavdar Ivanov
I was able to do a full build with a cvs update some 7 hours ago. Built-in Xorg is fine with AIGLX enabled now. On Sat, 6 Apr 2019 at 15:31, Patrick Welche wrote: > > On Sat, Apr 06, 2019 at 02:42:57PM +0100, Patrick Welche wrote: > > On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green

Re: Built-in vs. Modular Xorg under -current

2019-04-06 Thread Chavdar Ivanov
After a few reported breaks I was finally able to build 8.99.37 amd64. Xorg now works fine with AIGLX etc., so as far as I am concerned the latest Mesa 18.4 import plus the other llvm bits are working OK. The nouveau driver still does not work with my GeForce 950m, but I didn't expect it, the

Automated report: NetBSD-current/i386 build success

2019-04-06 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2019.04.06.15.35.09 kamil src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.105 2019.04.06.15.41.54 kamil src/tests/lib/libc/sys/t_fork.c,v 1.4

Re: /usr/tests/modules usage

2019-04-06 Thread Martin Husemann
On Sat, Apr 06, 2019 at 09:00:37AM -0700, Jason Thorpe wrote: > I originally but the thread pool test harness module in the kern/ > subdirectory, but then it got moved. > > *shrug* Originally I thought we would get very few modules for this kind of tests and put them in the standard modules set

Re: NetBSD-current/sparc build failure

2019-04-06 Thread Jason Thorpe
> On Apr 6, 2019, at 7:52 AM, Jason Thorpe wrote: > > >> /tmp/bracket/build/2019.04.06.11.54.25-sparc/tools/lib/gcc/sparc--netbsdelf/7.4.0/../../../../sparc--netbsdelf/bin/ld: >> disabling relaxation; it will not work with multiple definitions >> collect2: error: ld returned 1 exit status >>

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

2019-04-06 Thread maya
On Sat, Apr 06, 2019 at 02:52:06PM +0300, Andreas Gustafsson wrote: > The i386 build is still failing, but now in a different place: > > --- dependall-sys --- > /tmp/bracket/build/2019.04.06.09.33.07-i386/src/sys/compat/freebsd/freebsd_syscall.c: > In function 'freebsd_syscall': >

Re: /usr/tests/modules usage

2019-04-06 Thread Kamil Rytarowski
On 06.04.2019 18:00, Jason Thorpe wrote: > The thread pool module can probably be removed because I added a rump-based > test for that later. An extra test isn't a bad thing! I would keep it. signature.asc Description: OpenPGP digital signature

Re: /usr/tests/modules usage

2019-04-06 Thread Jason Thorpe
> On Apr 5, 2019, at 11:51 PM, Paul Goyette wrote: > > It seemts to me that the original intent of this directory was for > "things that [help] test the modules system". But recently we seem > to have acquired at least a couple entries here which are "module- > that-help-test-other-things".

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

2019-04-06 Thread Andreas Gustafsson
Christos Zoulas wrote: > Must be, but I can't reproduce it, can you run gdb on the core file? No need to go hunting or a core, simply running "date" with no arguments will reproduce it. Doing that under gdb shows: (gdb) where #0 0xac643b67 in ?? () from /lib/libc.so.12 #1 0xac644496 in

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

2019-04-06 Thread Christos Zoulas
Must be, but I can't reproduce it, can you run gdb on the core file? christos > On Apr 6, 2019, at 3:52 AM, Andreas Gustafsson wrote: > > NetBSD Test Fixture wrote: >> This is an automatically generated notice of new failures of the >> NetBSD test suite. >> >> The newly failing test cases

Re: NetBSD-current/sparc build failure

2019-04-06 Thread Jason Thorpe
> On Apr 6, 2019, at 5:59 AM, Andreas Gustafsson wrote: > > The sparc build is also failing, with a different error than i386 and amd64: > > /tmp/bracket/build/2019.04.06.11.54.25-sparc/tools/bin/sparc--netbsdelf-gcc > -shared -Wl,-soname,librump.so.0 -Wl,--warn-shared-textrel >

Re: Mesa update

2019-04-06 Thread Patrick Welche
On Sat, Apr 06, 2019 at 02:42:57PM +0100, Patrick Welche wrote: > On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green wrote: > > thanks for the original work and fixing this i386 thing! > > > > > If you would like to do an update build, you will likely have to remove > > > many directories in

Re: Mesa update

2019-04-06 Thread Patrick Welche
On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green wrote: > thanks for the original work and fixing this i386 thing! > > > If you would like to do an update build, you will likely have to remove > > many directories in OBJDIR/external/mit/xorg/lib/*. > > I didn't test this, sorry. > > you

NetBSD-current/sparc build failure

2019-04-06 Thread Andreas Gustafsson
The sparc build is also failing, with a different error than i386 and amd64: /tmp/bracket/build/2019.04.06.11.54.25-sparc/tools/bin/sparc--netbsdelf-gcc -shared -Wl,-soname,librump.so.0 -Wl,--warn-shared-textrel -Wl,-Map=librump.so.0.map

Re: /usr/tests/modules usage

2019-04-06 Thread Kamil Rytarowski
On 06.04.2019 08:51, Paul Goyette wrote: > It seemts to me that the original intent of this directory was for > "things that [help] test the modules system".  But recently we seem > to have acquired at least a couple entries here which are "module- > that-help-test-other-things". > It would be

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

2019-04-06 Thread Paul Goyette
On Sat, 6 Apr 2019, Paul Goyette wrote: My amd64 build failed with checkflist ===> distrib/sets == 3 missing files in DESTDIR Files in flist but missing from DESTDIR. File wasn't installed ? -- ./usr/tests/modules/t_ufetchstore

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

2019-04-06 Thread Paul Goyette
My amd64 build failed with checkflist ===> distrib/sets == 3 missing files in DESTDIR Files in flist but missing from DESTDIR. File wasn't installed ? -- ./usr/tests/modules/t_ufetchstore ./usr/tests/modules/ufetchstore_tester

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

2019-04-06 Thread Andreas Gustafsson
The i386 build is still failing, but now in a different place: --- dependall-sys --- /tmp/bracket/build/2019.04.06.09.33.07-i386/src/sys/compat/freebsd/freebsd_syscall.c: In function 'freebsd_syscall': /tmp/bracket/build/2019.04.06.09.33.07-i386/src/sys/compat/freebsd/freebsd_syscall.c:103:9:

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

2019-04-06 Thread Andreas Gustafsson
NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: > > atf/tools/atf-run_test:broken_results [...] Looking at the log for the first failing test, "date" is dumping core:

Automated report: NetBSD-current/i386 test failure

2019-04-06 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: atf/tools/atf-run_test:broken_results atf/tools/atf-run_test:broken_tp_list atf/tools/atf-run_test:exit_codes atf/tools/atf-run_test:expect

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

2019-04-06 Thread Andreas Gustafsson
The NetBSD Test Fixture wrote: > --- dependall-pkg_install --- > cc1: all warnings being treated as errors > *** [util.o] Error code 1 > nbmake[10]: stopped in > /tmp/bracket/build/2019.04.06.03.06.29-i386/src/external/bsd/pkg_install/sbin/pkg_create More relevant error messages

/usr/tests/modules usage

2019-04-06 Thread Paul Goyette
It seemts to me that the original intent of this directory was for "things that [help] test the modules system". But recently we seem to have acquired at least a couple entries here which are "module- that-help-test-other-things". Shouldn't the latter class be in the directory appropriate to

Automated report: NetBSD-current/i386 build failure

2019-04-06 Thread NetBSD Test Fixture
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.06.03.06.29. An extract from the build.sh output follows: