Hal Murray :
>
> > I'm pretty sure this is a problem with the ntpq code, not with Python -
> > Python in general has a reputation for being *easy* to read six months
> > later,
> > which I think is deserved. It's one of the first things I noticed when I
> > started coding in Python back in 1998
> I'm pretty sure this is a problem with the ntpq code, not with Python -
> Python in general has a reputation for being *easy* to read six months later,
> which I think is deserved. It's one of the first things I noticed when I
> started coding in Python back in 1998 or so.
The hard
When I start ntpq, I get this message:
ntp.ntpc wrong version '1.2.1+17-gbc270426b-dirty 2021-07-09/11:45:21' !=
'1.2.1'
It works OK.
That's built with
--build-desc=xxx on the configure line to waf
on a system using git with some local edits.
It works with the same command line on a
> The valid combinations of $GOOS and $GOARCH are:
> freebsd 386
> freebsd amd64
> freebsd arm
> netbsd386
> netbsdamd64
> netbsdarm
Interesting. No arm64.
Here is the Rust page:
https://doc.rust-lang.org/nightly/rustc/platform-support.html
--
Hal Murray :
> More topics for this discussion:
>
> What platforms is the new environment supported on? See my reply to Sanjeev
> Gupta's message.
>
> As far as I can tell, we don't have a list of supported/tested platforms. Is
> there an official we page that describes what we support? (I'm
More topics for this discussion:
What platforms is the new environment supported on? See my reply to Sanjeev
Gupta's message.
As far as I can tell, we don't have a list of supported/tested platforms. Is
there an official we page that describes what we support? (I'm expecting
something like
> The issue I have is that each time you add code, or James refactors to fix
> bugs, there might be an implicit, untracked, bump in the rustc version
> required. Although Fedora may be able to keep up, debian-backports, or
> anything but the latest Ubuntu, and certainly Solaris, would remain
