Yo Richard!
On Mon, 17 Feb 2020 16:15:36 -0600
Richard Laager wrote:
> > That looks like a Python crash while running waf code, which is
> > really weird. Googling that error message does show some results
> > for macOS, but nothing particularly illuminating.
>
> Never mind. Turns out it was
Yo Richard!
On Mon, 17 Feb 2020 16:15:36 -0600
Richard Laager wrote:
> On 2/17/20 1:34 PM, Gary E. Miller via devel wrote:
> > But, when I tried to build with git head, I now get this error:
> >
> > Waf: Leaving directory `/usr/local/src/NTP/ntpsec/build/main'
> > Fatal Python error: PyThreadSt
On 2/17/20 1:34 PM, Gary E. Miller via devel wrote:
> But, when I tried to build with git head, I now get this error:
>
> Waf: Leaving directory `/usr/local/src/NTP/ntpsec/build/main'
> Fatal Python error: PyThreadState_Get: no current thread
> ../Do-config-ntpsec: line 11: 13733 Abort trap: 6
On Mon, Feb 17, 2020 at 1:34 PM Gary E. Miller via devel
wrote:
> Yo Hal!
>
> On Sun, 16 Feb 2020 21:42:59 -0800
> Hal Murray via devel wrote:
>
> > wscript says:
> > # MacOS doesn't have timer_create ??
> > ('timer_create', ["signal.h", "time.h"], "RT", False),
> >
> > Can a Mac
Yo Hal!
On Sun, 16 Feb 2020 21:42:59 -0800
Hal Murray via devel wrote:
> wscript says:
> # MacOS doesn't have timer_create ??
> ('timer_create', ["signal.h", "time.h"], "RT", False),
>
> Can a MacOS wizard verify that and/or see what versions do/don't
> support it? Thanks.
I'm
e...@thyrsus.com said:
> I believe those #ifdefs are a port hack for a minor platform that's not
> completely standards-cimpliant, most likely some version og Mac OS/X.
Thanks.
wscript says:
# MacOS doesn't have timer_create ??
('timer_create', ["signal.h", "time.h"], "RT", Fals
Hal Murray via devel :
> devel/hacking.adoc says:
> You *may* use clock_gettime(2) and clock_settime(2) calls, and
> the related getitimer(2)/setitimer(2), from POSIX-1.2008.
>
> My man pages say both are in POSIX.1-2001.
>
> Is there any reason we don't pick one and discard the crufty ifdefs
devel/hacking.adoc says:
You *may* use clock_gettime(2) and clock_settime(2) calls, and
the related getitimer(2)/setitimer(2), from POSIX-1.2008.
My man pages say both are in POSIX.1-2001.
Is there any reason we don't pick one and discard the crufty ifdefs?
No big deal, just another minor cl
