Re: Catching up

2025-02-03 Thread Richard Laager via devel
On 2025-02-03 23:31, Hal Murray via devel wrote: Did you see my comment about how dropping Python 2 before getting rid of the polyXXX wrapers is dangerous, because removing the wrappers without properly fixing the underlying code is more likely to break Python 3 than Python 2? I'm concerned t

recvmsg() length report

2025-02-03 Thread Hal Murray via devel
Linux: x86-64:16 I don't have any really really old systems. x86-32: 8 Debien, 6.1.0-29-686-pae i686 Arm: 8 Arm64: 16 FreeBSD: x86-64: 20 <=== x86-32: 8 Arm: 16 Arm64: 20 <=== NetBSD: x86-64: 20 <=== x86-32: 12 Arm: 20 <=== long is 4, time_t is 8, timesp

Re: Catching up

2025-02-03 Thread Hal Murray via devel
> Did you see my comment about how dropping Python 2 before getting rid of > the polyXXX wrapers is dangerous, because removing the wrappers without > properly fixing the underlying code is more likely to break Python 3 than > Python 2? Yes, but I don't know enough about Python to know what it

Re: Catching up

2025-02-03 Thread Fred Wright via devel
On Mon, 3 Feb 2025, Hal Murray via devel wrote: Uh, yes. I'll continue to object. It buys us nothing now, and it will annoy some people. Maybe later this year. OK. I guess I missed your previous objections. Have we actually made contact with anybody using python2 (and NTPsec)? Should w

Re: Catching up

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Mon, 03 Feb 2025 20:08:46 -0800 Hal Murray wrote: > > Uh, yes. I'll continue to object. It buys us nothing now, and it > > will annoy some people. Maybe later this year. > > OK. I guess I missed your previous objections. > > Have we actually made contact with anybody using py

Re: cross armhf tangle

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Mon, 03 Feb 2025 19:59:41 -0800 Hal Murray wrote: > The current code in wafhelpers/check_sizeof.py seems to work. > > There are 2 reasons I would like to keep and understand it. One is > general curiousity. It was commited by ESR and he is usually very > good about fixing crappy c

Re: cross armhf tangle

2025-02-03 Thread Hal Murray via devel
The current code in wafhelpers/check_sizeof.py seems to work. There are 2 reasons I would like to keep and understand it. One is general curiousity. It was commited by ESR and he is usually very good about fixing crappy code. My best guess is that it was part of a large chunk that was copie

Re: Catching up

2025-02-03 Thread Hal Murray via devel
> Uh, yes. I'll continue to object. It buys us nothing now, and it will > annoy some people. Maybe later this year. OK. I guess I missed your previous objections. Have we actually made contact with anybody using python2 (and NTPsec)? Should we put a note in NEWS saying this is the last re

Re: cross armhf tangle

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Sun, 02 Feb 2025 20:40:43 -0800 Hal Murray wrote: > The unobvious part is the code in wafhelpers/check_sizeof.py that > handles the cross case for getting NTP_SIZEOF_TIME_T and friends. NTP_SIZEOF_TIME_T is in the code 5 times, in just 3 places. ./ntpd/ntp_leapsec.c:#if NTP_SIZEOF

Re: Catching up

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Fri, 31 Jan 2025 16:14:07 -0800 Hal Murray via devel wrote: > I think we should drop support for python 2 before this release. Any > objections? Uh, yes. I'll continue to object. It buys us nothing now, and it will annoy some people. Maybe later this year. RGDS GARY ---

Wish list for release

2025-02-03 Thread Hal Murray via devel
It would be really nice if we had a working example of a cross compile, and something like a HOWTO-cross to document it, including the packages that need to be installed. It would be nice if option-tester could also do an install, bin-test, and uninstall. Best in a scratch directory. -- T

Re: cross armhf tangle

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Sun, 02 Feb 2025 20:40:43 -0800 Hal Murray wrote: > The unobvious part is the code in wafhelpers/check_sizeof.py that > handles the cross case for getting NTP_SIZEOF_TIME_T and friends. The fix is to just remove that test. Just use sizeof(time_t) in the code instead of trying to fig

Re: cross armhf tangle

2025-02-03 Thread Gary E. Miller via devel
Yo Hal! On Sun, 02 Feb 2025 21:35:02 -0800 Hal Murray wrote: > >> That was my first try. It didn't work on BSD. > > Care to share what the failure was? > > It didn't know what a struct timeval was. Did you set the required defines first? Any place I can go to see the BSD man page and the

Re: Windows and other AEAD ciphers

2025-02-03 Thread Hal Murray via devel
Neat. Thanks. > - libm > - stdbool.h Those should be part of the POSIX environment. At worst, we can clone stdbool.h and find the source for libm and grab the parts we need. > - struct timex and two of its members This will be the tricky part. I'm expecting a small shim to translate ntp_adjt

Windows and other AEAD ciphers

2025-02-03 Thread James Browning via devel
Building on windows will cause pain in the neck. Microsoft's SDK coaster image is a gigabyte and a half compressed. However, after too much frustration, I got an unrelated toy program to build on Linux. Building NTPsec on Linux but for Windows would require us to either bring back or re-impleme