Re: Can't cross-build on macOS: clock.h

2023-10-26 Thread Martin Husemann
On Fri, Oct 27, 2023 at 08:49:53AM +0200, Tobias Nygren wrote: > The header being used from the tools build was an unexpected surprise > but such reasons are why those ifdef guards exist. So I think it > just just be put back the way it was. The example came from > sys/atomic.h so it shouldn't be c

Re: Can't cross-build on macOS: clock.h

2023-10-26 Thread Tobias Nygren
On Fri, 27 Oct 2023 08:03:48 +0200 Adam wrote: > Greetings, > > This change: > > --- clock.h 26 Oct 2023 00:59:16 - 1.5 > +++ clock.h 26 Oct 2023 14:04:45 - 1.6 > @@ -1,4 +1,4 @@ > -/* $NetBSD: clock.h,v 1.5 2023/10/26 00:59:16 jschauma Exp $ */ > +/* $NetBSD: clock.h,v 1.6 2023/10/26 1

Can't cross-build on macOS: clock.h

2023-10-26 Thread Adam
Greetings, This change: --- clock.h 26 Oct 2023 00:59:16 - 1.5 +++ clock.h 26 Oct 2023 14:04:45 - 1.6 @@ -1,4 +1,4 @@ -/* $NetBSD: clock.h,v 1.5 2023/10/26 00:59:16 jschauma Exp $ */ +/* $NetBSD: clock.h,v 1.6 2023/10/26 14:04:45 jschauma Exp $ */ /*- * Copyright (c) 1996 The NetBSD

daily CVS update output

2023-10-26 Thread NetBSD source update
Updating src tree: U src/crypto/external/bsd/openssh/dist/moduli P src/share/man/man4/mcx.4 P src/share/misc/acronyms.comp P src/sys/arch/sparc/conf/files.sparc P src/sys/arch/sparc/include/db_machdep.h P src/sys/arch/sparc/sparc/db_interface.c P src/sys/dev/ic/dwc_eqos.c P src/sys/dev/ic/dwc_eqo

Automated report: NetBSD-current/i386 build success

2023-10-26 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the first successful build: 2023.10.26.15.10.14 christos src/crypto/external/bsd/openssh/dist/moduli 1.10 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/com

Re: sys/clock.h

2023-10-26 Thread Jan Schaumann
Simon Burge wrote: > +#if !defined(_KERNEL) && !defined(_STANDALONE) > +#include > +#endif > > Sorry for chiming in late. Wouldn't it be better to include > and avoid the #ifdef? Especially since > is a symlink to . That makes sense to me - made it so. :-) Thanks! -Jan

Re: sys/clock.h

2023-10-26 Thread Simon Burge
Hi Jan, Jan Schaumann wrote: > > It looks like in order to be able to use sys/clock.h, > > one needs to first include either inttypes.h or > > stdint.h _before_ sys/clock.h. > > > > I've long made it a habit of sorting includes > > alphabetically and according to /usr/share/misc/style, > > which