Automated report: NetBSD-current/i386 build success

2021-08-08 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: 2021.08.09.04.06.21 thorpej src/sys/dev/acpi/acpi_i2c.h,v 1.4 2021.08.09.04.07.29 thorpej src/sys/arch/macppc/dev/smuiic.c,v 1.10 2021.08.09.04.07.29

Re: daily CVS update output

2021-08-08 Thread Jason Thorpe
> On Aug 8, 2021, at 8:28 PM, bch wrote: > > > cvs update: `src/sys/dev/acpi/acpi_i2c.h' is no longer in the repository > > > This is still wanted by acpi_i2c.c CVS did the Wrong Thing (SHOCKER). Should be fixed now. Thanks for bringing it to my attention!! -- thorpej

daily CVS update output

2021-08-08 Thread NetBSD source update
Updating src tree: P src/bin/sh/var.c P src/common/lib/libc/arch/aarch64/atomic/__aarch64_lse.S P src/doc/BRANCHES P src/doc/CHANGES P src/lib/libc/net/getpeereid.c P src/lib/libc/rpc/svc_vc.c P src/lib/libc/sys/getsockopt.2 P src/lib/libperfuse/perfuse.c P src/regress/sys/kern/unfdpass/unfdpass.

Automated report: NetBSD-current/i386 build failure

2021-08-08 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 2021.08.09.00.32.51. An extract from the build.sh output follows: --- OsdMisc.d --- #create GENERIC/OsdMisc

Re: lang/mono or futex problem

2021-08-08 Thread Chuck Silvers
On Sun, Aug 01, 2021 at 02:42:59PM +0100, Robert Swindells wrote: > > Thomas Klausner wrote: > >I've just tried updating the .net program 'torrentzip' > >(archivers/torrentzip) to the latest version. The current pkgsrc > >version can be run by calling 'mono' on it (the package installs a > >wrapp

Re: Orange pi support for i2c

2021-08-08 Thread Dave Tyson
On Sunday 08 Aug 2021 08:31:57 Martin Husemann wrote: > On Sat, Aug 07, 2021 at 09:54:40PM +, Dave Tyson wrote: > > One other issue I noted with the latter two boards is that ethernet no > > longer works - this may be related to changes to the phy support > > introduced in 2019, but I will onl