Re: GCC 9 enabled for x86 and arm platforms.

2020-09-13 Thread David Holland
On Sun, Sep 13, 2020 at 07:13:31PM +1000, matthew green wrote: > > Would -r flag in build.sh command be sufficient to ensure a clean build? > > > > Something like > > ===> build.sh command:./build.sh -m amd64 -B nb899-20190723 -M ../obj > > -T ../tooldir -r -U distribution kernel=SANDY7

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

2020-09-13 Thread Robert Elz
Date:Sun, 13 Sep 2020 22:14:00 +0100 From:Roy Marples Message-ID: | >| > net/arp/t_arp:arp_proxy_arp_pub | >| > net/arp/t_arp:arp_proxy_arp_pubproxy | > | > Those two are still failing. | | Works fine on my box. | Can you say how the

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

2020-09-13 Thread Roy Marples
On 13/09/2020 22:07, Robert Elz wrote: Date:Sun, 13 Sep 2020 20:06:45 +0100 From:Roy Marples Message-ID: <9e977478-d209-2dbb-49d9-3fa9acd25...@marples.name> | > net/arp/t_arp:arp_cache_expiration_10s | > net/arp/t_arp:arp_cache_expiration_5s Thos

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

2020-09-13 Thread Robert Elz
Date:Sun, 13 Sep 2020 20:06:45 +0100 From:Roy Marples Message-ID: <9e977478-d209-2dbb-49d9-3fa9acd25...@marples.name> | > net/arp/t_arp:arp_cache_expiration_10s | > net/arp/t_arp:arp_cache_expiration_5s Those two are "fixed" (if you can call deleted fix

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

2020-09-13 Thread Roy Marples
On 12/09/2020 22:57, NetBSD Test Fixture wrote: This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: net/arp/t_arp:arp_cache_expiration_10s net/arp/t_arp:arp_cache_expiration_5s net/arp/t_arp:arp_command net/ar

Automated report: NetBSD-current/i386 build success

2020-09-13 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: 2020.09.13.13.03.15 rillig src/distrib/sets/lists/tests/mi,v 1.922 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.09.html#

Automated report: NetBSD-current/i386 build failure

2020-09-13 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 2020.09.13.09.43.01. An extract from the build.sh output follows: cd /tmp/bracket/build/2020.09.13.09.43.01-i386/src

Re: GCC 9 enabled for x86 and arm platforms.

2020-09-13 Thread Patrick Welche
On Sun, Sep 13, 2020 at 07:28:16AM +, Thomas Mueller wrote: > > i've switched x86 and arm to GCC 9. several others are liking > > to switch soon, and they will all likely need clean builds to > > be stable. > > > please send email here or to me or send-pr for problems. > > > thanks!

re: GCC 9 enabled for x86 and arm platforms.

2020-09-13 Thread matthew green
> Would -r flag in build.sh command be sufficient to ensure a clean build? > > Something like > ===> build.sh command:./build.sh -m amd64 -B nb899-20190723 -M ../obj -T > ../tooldir -r -U distribution kernel=SANDY7 this is probably good enough. -r removes tooldir and destdir. the lack of -

Re: GCC 9 enabled for x86 and arm platforms.

2020-09-13 Thread Thomas Mueller
> i've switched x86 and arm to GCC 9. several others are liking > to switch soon, and they will all likely need clean builds to > be stable. > please send email here or to me or send-pr for problems. > thanks! > .mrg. Would -r flag in build.sh command be sufficient to ensu