On Fri, 1 Aug 2025, Hal Murray wrote:
devel@ntpsec.org said:
Usually, you won't get that type of warning unless you enable it. And
usually, you only get that type of warning in an optimized compile, since
the dataflow analysis needed to detect it is part of the optimization
code.
I tried
On Tue, 29 Jul 2025, Hal Murray via devel wrote:
Are we missing one?
I had a typo. I was using an uninitialized variable. Modern compilers
didn't complain. Old ones did. (I don't set any compiler or loader
flags.)
What gets checked isn't a monotonic function of the compiler version.
Te
On Mon, 14 Apr 2025, Hal Murray wrote:
If the values are identical, then it's not functionally incorrect, but
it's certainly conceptually incorrect to compare an SO_* value to a
cmsg_type field. And if the values are identical, it wouldn't change the
behavior to use the correct name.
Sorry
I was just looking at recent changes, and came across commit 4756b6317.
I don't know anything specifically about the *_TIMESTAMPNS_OLD stuff, but
I do know that the SO_* symbols are for the socket options and the SCM_*
symbols are for the CMSG types, so I don't see how this could possibly be
On Mon, 14 Apr 2025, Hal Murray wrote:
I do know that the SO_* symbols are for the socket options and the SCM_*
symbols are for the CMSG types, so I don't see how this could possibly be
correct. Note the code immediately above it.
The OLD stuff is a mess.
I did it the way you expect, but
On Sun, 30 Mar 2025, Fred Wright wrote:
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 4:44:51 PM Pacific Daylight Time Fred Wright via
devel wrote:
I'm not sure what you mean by "my patches", given that I've never
submitted any for th
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 4:44:51 PM Pacific Daylight Time Fred Wright via
devel wrote:
I'm not sure what you mean by "my patches", given that I've never
submitted any for this issue, though I'd suggested what suc
On Tue, 1 Apr 2025, Gary E. Miller via devel wrote:
On Mon, 31 Mar 2025 20:52:30 -0700
Hal Murray wrote:
[...]
Alternatively, you can create a link to you python3, called python.
Like so:
ln -s /usr/bin/python3 /usr/bin/python
That command line doesn't work on FreeBSD or NetBSD
Yeah, *B
On Tue, 1 Apr 2025, James Browning via devel wrote:
On Monday, March 31, 2025 8:52:30 PM Pacific Daylight Time Hal Murray via
devel wrote:
buildprep has some python2 cruft. I ignored it.
Should we announce that it no longer works for python 2 and clean it up a
bit?
Don't let Fred, Gary or
On Mon, 31 Mar 2025, Hal Murray via devel wrote:
+Alternatively you can link your python3 to python.
+`ln -s /usr/bin/python3 /usr/bin/python`
That "to" looks backwards to me. I expect:
link python to your python3
Yes, but 'ln' is like 'cp', so you put the source first.
Fred Wright
__
On Sun, 30 Mar 2025, Fred Wright wrote:
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 5:00:57 PM Pacific Daylight Time Fred Wright via
devel wrote:
Actually, to be fair, I didn't find a file actually called 'waf' in the
upstream repo, b
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 5:00:57 PM Pacific Daylight Time Fred Wright via
devel wrote:
Actually, to be fair, I didn't find a file actually called 'waf' in the
upstream repo, but I did find a 'wscript' shebanged
On Sat, 29 Mar 2025, Fred Wright via devel wrote:
On Sat, 29 Mar 2025, James Browning via devel wrote:
Pass; as an alternative, I would drop the exposition in a subsection in
INSTALL.adoc; removing only the one byte, leaving the newly incorrect
signature intact. Then commit that pottage
On Sun, 30 Mar 2025, James Browning via devel wrote:
On Sunday, March 30, 2025 4:20:12 PM Pacific Daylight Time Fred Wright via
devel wrote:
I'd actually been assuming that the incorrect 'python3' shebang line was
from upstream. I hadn't realized that the upstream versio
On Sat, 29 Mar 2025, James Browning via devel wrote:
On Saturday, March 29, 2025 1:52:15 PM Pacific Daylight Time Fred Wright via
devel wrote:
How many people care about signatures *and* don't trust the ntpsec
signature *and* worry about the waf signature?
None, Probably. I'm tryi
On Fri, 28 Mar 2025, James Browning via devel wrote:
On Thursday, March 27, 2025 9:29:33 PM Pacific Daylight Time Fred Wright via
devel wrote:
On Fri, 28 Mar 2025, Matt Selsky wrote:
[...]
What specifically is currently shebanged to python3 and maybe needs to be
changed?
I'm referri
On Thu, 27 Mar 2025, Hal Murray via devel wrote:
There are definitely systems with python3 and no python. Eg, Debian 12
for example.
Some (most?) distros have a tiny package that sets up python to go to
python3.
On Debian, it's python-is-python3, and buildprep installs it.
On Fedora, it's
On Fri, 28 Mar 2025, Matt Selsky wrote:
On Thu, Mar 27, 2025 at 02:48:54PM -0700, Fred Wright via devel wrote:
I've confirmed that it works with Python 2.7, including building the
extension. That means that shebanging it to 'python3' is inappropriate,
unless there are
On Thu, 27 Mar 2025, Hal Murray via devel wrote:
Please remove the older waf binary and replace the symlink with the newer waf
binary itself.
OK. Done.
I've confirmed that it works with Python 2.7, including building the
extension. That means that shebanging it to 'python3' is inapprop
On Tue, 11 Feb 2025, Hal Murray wrote:
For example, I just submitted an MR to fix a warning for something which
is perfectly legal, but which broke the build here due to -Werror.
Thanks. Just curious. What OS/Distro found that?
It's clang 6. The OS doesn't enter into it.
Turning on -W
On Sat, 8 Feb 2025, Hal Murray via devel wrote:
waf configure --help says:
--enable-warnings Enable annoying CC warnings
Are they really annoying? My normal build script turns it on without
problems.
I've certainly seen warnings without that option, so it probably just
means "enabl
On Fri, 7 Feb 2025, Hal Murray via devel wrote:
Sigh. It needs a dose of TLC.
The Downloads section has 2 URLs.
The first one is https://gitlab.com/groups/NTPsec
git clone on that one doesn't work.
That's the URL for the group's homepage, not the project's homepage, which
is:
On Tue, 4 Feb 2025, Hal Murray wrote:
As Alice would say, "curiouser and curiouser". Just when I think I've
figured out the reason for one bit of bizarreness, you find another. :-)
I think the current code works on all my systems.
What's the breakdown in the 32-bit NetBSD case? One wou
On Tue, 4 Feb 2025, Richard Laager via devel wrote:
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 like
On Mon, 3 Feb 2025, Hal Murray via devel wrote:
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 <
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
ather than using what already works, or newer versions from people who
actually think that breaking things is a bad idea (unlike the python.org
folks).
On 2025-01-30 18:19, Fred Wright via devel wrote:
It's not about whether Python 3 is available, but about whether it's
usable for wha
On Wed, 29 Jan 2025, Hal Murray wrote:
It's not about "with" in the sense of what's on the system; it's about
what Python version *their code* works with. Due to the large
incompatibilities between Python 2 and Python 3, it takes serious work to
update existing Python 2 code to work with Pyth
On Wed, 29 Jan 2025, Gary E. Miller via devel wrote:
On Tue, 28 Jan 2025 20:05:11 -0800
Hal Murray via devel wrote:
Gary said:
And yet, we still get complaints. There are maintained Python 2.7
forks that some distros still use and update.
I've seen at least one distro that had python 3 b
On Tue, 24 Dec 2024, Gary E. Miller via devel wrote:
On Tue, 24 Dec 2024 15:21:14 -0800 (PST)
Fred Wright via devel wrote:
On Tue, 24 Dec 2024, Gary E. Miller (@garyedmundsmiller) wrote:
Gary E_ Miller
commented:
https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1414#note_2273464732
I
On Tue, 24 Dec 2024, Gary E. Miller (@garyedmundsmiller) wrote:
Gary E_ Miller commented:
https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1414#note_2273464732
I don't know about OSX, but this is not the proper GNU libc fix.
With GNU libc, the size of time_t on 32-bit ABI depends on two #
On Wed, 18 Dec 2024, Hal Murray wrote:
Fred Wright said:
I'm always in favor of maximum compatibility.
There is a tradeoff between broader compatibility and clutter in the code.
Indeed, though a good design keeps aspects dependent on the OS or other
outside packages well-segregated.
On Sun, 22 Dec 2024, Hal Murray wrote:
The macro to map EVP_MD_CTX_reset to EVP_MD_CTX_init wouldn't have
worked, but it didn't matter since that function isn't actually used. I
didn't think it was a good idea to leave a time bomb for some possible
future use, so I fixed it.
I would just
On Fri, 20 Dec 2024, Hal Murray wrote:
Pleae try again.
Looks like I had the #define backwards.
I copied that code from new defs which was trying to adapt to old code.
We want old defs to reverse adapt to new code.
I should have noticed that, but I was in the middle of doing three things
On Thu, 19 Dec 2024, Hal Murray wrote:
Fix pushed. Please give it a try.
Not there yet. Sample from Fedora 25:
=
[219/265] Compiling libntp/pymodule-mac.c
In file included from ../../libntp/pymodule-mac.c:16:0:
../../i
On Wed, 18 Dec 2024, Hal Murray wrote:
It used to be possible to build with --disable-nts when a sufficiently
new OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not
sure why cryptographic functions are needed at all with --disable-nts,
but even if they are, the compatibility d
It used to be possible to build with --disable-nts when a sufficiently new
OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not sure
why cryptographic functions are needed at all with --disable-nts, but even
if they are, the compatibility definitions could have been in a single
On Fri, 13 Dec 2024, Gary E. Miller via devel wrote:
On Fri, 13 Dec 2024 05:46:32 +
Matt Selsky via devel wrote:
math.isfinite() was added in Python 3.2
per https://docs.python.org/3/library/math.html.
Should we use math.isinf() instead in order to retain Python 2
compatibility until we
On Wed, 11 Sep 2024, Hal Murray via devel wrote:
I'm trying to cleanup the tangle in ntp_control.c that generates warnings.
They may be actual bugs. The problem is that the man page says long while
the actual size may be 32 or 64 on 32 bit Linux systems.
If I knew the size, the fix would be
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
Does #ifdef work on functions? I thought not, but the old code looks like
its doing that.
It only works when the apparent functions are macros. The preprocessor
knows nothing about functions.
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
On Tue, 25 Jun 2024, Hal Murray via devel wrote:
$ grep rtems wscript */wscript wafhelpers/*
wscript:if ctx.options.enable_rtems_trace:
wscript:ctx.find_program("rtems-tld", var="BIN_RTEMS_TLD",
wscript: path_list=[ctx.options.rtems_trace_path,
wscript:# Bor
On Fri, 21 Jun 2024, Hal Murray via devel wrote:
Does anybody other than me run/test on NetBSD?
Ocasionally. I have a NetBSD 6.1.5 VM.
The test-all part of option-tester gets the following error.
Why only in option-tester?
ntp_stdlib includes signal.h
Do we have to do some magic to ma
On Thu, 2 May 2024, Hal Murray via devel wrote:
Note that for AT&T, the normal case of an NTP client goes through NAT so
NTP isn't using port 123 and doesn't get blocked.
Many, if not most, NAT implementations avoid remapping "privileged" client
ports, on the theory that specific port numbe
On Wed, 3 Jan 2024, Matthew Selsky wrote:
On Tue, Jan 02, 2024 at 08:52:53PM -0800, Fred Wright via devel wrote:
It should, though if the timestamps get updated in the process it would
trade bad name ordering for bad timestamp ordering. The ideal thing would
be to fix the names but keep the
On Tue, 2 Jan 2024, Hal Murray via devel wrote:
Fred Wright said:
[context is my reply to the released message.]
For some reason the antecedent to this message wasn't sent to the list,
though I'd noticed the release by checking the repo.
My copy was sent to:
Subject: NTPsec 1.2.3 released
On Wed, 3 Jan 2024, Matthew Selsky wrote:
On Tue, Jan 02, 2024 at 07:21:39PM -0800, Fred Wright via devel wrote:
There are a couple of minor issues that I should have noticed in the RC but
didn't:
1) The 1.2.2a entry is missing from NEWS. This is presumably because of the
way the
On Sat, 30 Dec 2023, Hal Murray via devel wrote:
Thanks.
and thanks to all who contributed and tested.
For some reason the antecedent to this message wasn't sent to the list,
though I'd noticed the release by checking the repo.
There are a couple of minor issues that I should have notic
On Mon, 25 Dec 2023, Fred Wright via devel wrote:
Commit 07231d10e2 to add cipher-find also added exp-timing.c to the build
list but didn't actually add a source for it. Thus the attic build fails.
It probably makes sense to fix this before the release since it's a
regressio
Commit 07231d10e2 to add cipher-find also added exp-timing.c to the build
list but didn't actually add a source for it. Thus the attic build fails.
It probably makes sense to fix this before the release since it's a
regression and also doesn't affect any normally installed components, and
On Thu, 21 Dec 2023, Hal Murray wrote:
Let's put that stuff on the back burner until the release is out.
Agreed for OpenBSD per se, though it might be worth trying to determine
whether the apparent fencepost error with OPENSSL_VERSION_NUMBER is really
OpenBSD-specific, or a more general pr
On Thu, 21 Dec 2023, Fred Wright via devel wrote:
I found one build error that's a regression - in OpenBSD 5.6. It's
"'CMAC_CTX' undeclared" in authreadkeys.c, which is due to the new
conditional around the inclusion of . Some other sources
include this unc
I found one build error that's a regression - in OpenBSD 5.6. It's
"'CMAC_CTX' undeclared" in authreadkeys.c, which is due to the new
conditional around the inclusion of . Some other sources
include this unconditionally, and macencrypt.c has it in an if/else
construct. The else case there
On Mon, 18 Dec 2023, Hal Murray via devel wrote:
James said:
It sounds like a race condition in our wscript files or waf. How willing are
you to sink time into this, I think it's a losing proposition.
I've got a --jobs=1 in my script. That was added to make sure the printout
was easy to rea
On Mon, 18 Dec 2023, Fred Wright wrote:
On Mon, 18 Dec 2023, Matthew Selsky wrote:
On Sun, Dec 17, 2023 at 08:17:23PM -0800, Fred Wright via devel wrote:
There are also a bunch of warnings with some compilers, which might be
worth
looking at. They're often fairly easy to fix, and some
it would be heavy-handed
for the normal build procedure. Or even having CI tests both ways might
be useful, to distiguish between errors and warnings. Though if CI tests
had the ability to report error versus warning results, that would be
unnecessary.
On Mon, 18 Dec 2023, Matthew Selsky w
On Wed, 6 Dec 2023, Matthew Selsky via devel wrote:
Sounds good. I'll aim to release ~15-Dec-2023.
Fortunately this hasn't happened yet. :-)
The main issue I've found is that the "struct var" in ntp_control.c, is
relying on anonymous unions, which are a relatively new language feature.
Th
On Sat, 18 Nov 2023, Fred Wright via devel wrote:
[...]
With or without this problem, it's a bad idea to combine multiple
unrelated changes into a single MR anyway. It's best to stick to one
topic per branch, both locally and in any MRs derived from such
branches.
I neglected t
In general, it's a good idea to read an actual book on git, rather than
trying to understand it purely through manpages. The one I used (almost a
decade ago) is this one:
https://www.amazon.com/gp/product/1449316387/
It doesn't tell you everything you might want to know, but it cov
On Fri, 4 Aug 2023, James Browning via devel wrote:
On 08/04/2023 6:35 PM PDT Fred Wright via devel wrote:
:::snip:::
I notice that the two commits for that don't seem to be in any branch.
Having commits only "owned" by a tag and not a branch seems fragile.
I do
On Fri, 4 Aug 2023, Fred Wright via devel wrote:
On Fri, 4 Aug 2023, Matthew Selsky wrote:
On Fri, Aug 04, 2023 at 01:47:29PM -0700, Fred Wright via devel wrote:
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
1.2.2a is 1.2.2 + the 2 line
On Fri, 4 Aug 2023, Matthew Selsky wrote:
On Fri, Aug 04, 2023 at 01:47:29PM -0700, Fred Wright via devel wrote:
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
1.2.2a is 1.2.2 + the 2 line patch to avoid the crash. We'll releas
On Thu, 3 Aug 2023, Hal Murray via devel wrote:
Should that also go to users@ and devel@?
What fraction of people on users or devel are also on announce?
And for that matter, what exactly is 1.2.2a, given that there's no git tag
for that version?
Fred Wright
_
On Sun, 23 Jul 2023, Hal Murray via devel wrote:
git log on a fresh clone shows things like this:
Author: Hal Murray
Date: Tue Jul 4 15:16:47 2023 -0700
Squash warnings about not handled enumeration
I haven't used that email in ages. My profile has been updated. Mail from
gitlab goe
On Mon, 2 Jan 2023, folkert via devel wrote:
[...]
It makes it include the delay in the json output.
Note that the delay is not the full story in the time uncertainty. A
long-standing ntpdig bug is that it fails to include the dispersion. The
delay gives the uncertainty in the server->cl
On Tue, 3 Jan 2023, folkert wrote:
Lost me. What about sntp do you want to put on gitlab?
Oh, reading these in reverse order. I think you are offering to
add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeling with
gi
On Tue, 3 Jan 2023, folkert via devel wrote:
Lost me. What about sntp do you want to put on gitlab?
Oh, reading these in reverse order. I think you are offering to
add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeli
On Wed, 21 Dec 2022, Hal Murray via devel wrote:
Google says:
https://developers.google.com/time/smear
We encourage anyone smearing leap seconds to use a 24-hour linear smear from
noon to noon UTC.
There were earlier versions which did sine rather than linear.
Hmm. I don't recall any non
On Wed, 21 Dec 2022, Fred Wright via devel wrote:
On Wed, 21 Dec 2022, Hal Murray wrote:
I guess if you don't see the issue I'll have to look more closely; I
thought
you might "just know" the problem.
Does git head work on 3.0?
Yes. I think it gets confused when
On Wed, 21 Dec 2022, Hal Murray wrote:
f...@fwright.net said:
It's 1.1.1s, which is the latest 1.1. I don'think there's anything
nonstandard besides using versioned install locations so that multiple
versions can be installed side-by-side.
I poked around some more. I have it building and r
On Wed, 21 Dec 2022, Hal Murray wrote:
but if breaking OpenSSL 1.1 was unintentional, then it needs to be fixed
I'm not aware of any intententional breakage. I'm pretty sure we would have
done it at configure time.
I don't think *unintentional* breakage would be done at configure time.
On Wed, 21 Dec 2022, Hal Murray via devel wrote:
Does anybody use it?
Do any distros build with it enabled?
Should we add an "#warn untested" to the code?
If some systems need leap-smeared time to get around bugs in their code,
they should be free to implement an *internal* leap-smeared tim
The build currently fails when building againts OpenSSL 1.1. MacPorts is
currently building it that way since the last release failed to build
against OpenSSL 3 (due to the attic problem), though it should be able to
move to OpenSSL 3 on the next release. So it's not actually an issue for
On Wed, 21 Dec 2022, Matt Selsky via devel wrote:
This is only a 2 minute delay, if I converted all timestamps to UTC correctly.
My last post was delayed 11 minutes, which is longer than it should be,
but not awful.
I did find that a spammer was abusing our Mailman instance's web
interfa
On Mon, 19 Dec 2022, James Browning via devel wrote:
On 12/18/2022 6:02 PM PST Hal Murray via devel wrote:
The commit message for that is lacking the blank line after the summary
line. This means that some git tools treat the entire commit message as the
summary, creating obnoxiously long li
On Sat, 17 Dec 2022, Hal Murray via devel wrote:
I just pushed code to save 10 NTS keys used to make cookies.
The commit message for that is lacking the blank line after the summary
line. This means that some git tools treat the entire commit message as
the summary, creating obnoxiously l
On Thu, 15 Dec 2022, Matthew Selsky via devel wrote:
On Wed, Dec 14, 2022 at 03:39:29PM -0800, James Browning via devel wrote:
'Do not apply transform to symbolic link targets' [1] Which I
got from googling 'gnu tar transform' IIRC. It is also a
gnuism, but I do not see a portable transform t
On Thu, 8 Dec 2022, James Browning via devel wrote:
Selsky broke the build[1] back in May 2020 when switching the
python_scripts variable in /wscript to a set when Python 2.6
does not support sets. Given the lack of complaints, I suspect
no one uses 2.6 anymore, which can be dropped.
Python
On Tue, 15 Feb 2022, Hal Murray via devel wrote:
matthew.sel...@twosigma.com said:
Are we worried about the speed of the build, lack of build support on
particular platforms, or something else?
I'm not particularly concerned about the speed of a build. As far as I know,
nobody has complain
On Fri, 27 Aug 2021, MLewis via devel wrote:
"
A new set of patches submitted to the Linux kernel mailing list summarises
the progress of the project to enable Rust to be used alongside C for
implementing the Linux kernel.
[...]
"
There's a YouTube video of a talk on this subject. It's
On Sun, 14 Mar 2021, Hal Murray via devel wrote:
[Context is cleaning up ntp_control]
This will probably be simple after somebody gives me a good example and/or
explains things to me.
I want to put a (pointer to a) function in a field of a struct.
The type of that function includes a pointer
On Thu, 17 Dec 2020, Eric S. Raymond wrote:
James Browning via devel :
The ntpsec forks belonging to rlaager, selsky, and ianbreune are still
detached. A quick check shows that there are no forks. The page I looked at
claimed that such detached repositories cannot be reattached. TLDR there is
On Sat, 12 Dec 2020, James Browning via devel wrote:
On Sat, Dec 12, 2020, at 6:41 PM Gary E. Miller via devel
wrote:
Yo James!
On Sat, 12 Dec 2020 18:35:13 -0800
James Browning via devel wrote:
The following patch clears it up on the machine I bisected on.
No, that uses the installed
On Wed, 14 Oct 2020, Hal Murray via devel wrote:
I'm setting up a new Debian system. I'm far from a Debian wizard, but I'm not
a total newbie either.
I have a ntp.pth setup, so ntpq finds the python libraries.
[...]
File "/usr/local/lib/python3/dist-packages/ntp/ntpc.py", line 49, in _dlo
On Wed, 2 Sep 2020, Hal Murray via devel wrote:
As of 1.1.9, NTPsec doesn't build "normally" on Debian 7...
Debian 7 is pretty old. Support ended May 2018
Do we want to support versions of distros that the vendor doesn't support any
more? My vote would be no.
There are sometimes signifi
On Thu, 3 Sep 2020, Hal Murray wrote:
I don't see how to use your master/entry macros to solve my problem.
I didn't mean for those to be usable as is, but just as an illustration of
the concept. YMMV.
The current code has only one table but it needs a symbol for the offset of
each slot
On Sun, 30 Aug 2020, Hal Murray via devel wrote:
Is there any way to do something like
#define FOO $FOO+1
I want to keep track of the number of times a macro has been called. That
seems like something that would happen often enough that there would be a
standard recipe but I haven't seen it.
On Tue, 16 Jun 2020, Mike Simpson via devel wrote:
There is libressl from the OpenBSD team
https://www.libressl.org/
It was forked from openssl in 2014
The last time I tried it, libaes_siv wouldn't build with LibreSSL, so that
would need to be fixed. Unless LibreSSL provides an adequate A
On Thu, 16 Apr 2020, Hal Murray via devel wrote:
Because RS232 signaling is negative logic.
That's what I used to think, but somebody corrected me many years ago.
The data is upside down but the control signals are not.
From https://en.wikipedia.org/wiki/RS-232
under Voltage levels
For d
On Sat, 31 Aug 2019, Matthew Selsky wrote:
On Fri, Aug 30, 2019 at 08:01:59PM -0700, Fred Wright via devel wrote:
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies
On Fri, 30 Aug 2019, Fred Wright via devel wrote:
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies type 'unsigned
short' but the argument has type &#x
On Thu, 29 Aug 2019, Gary E. Miller via devel wrote:
Warnings on OSX:
[ 73/131] Compiling libntp/ntp_calendar.c
../../ntpd/ntp_control.c:2612:27: warning: format specifies type 'unsigned
short' but the argument has type 'unsigned int' [-Wformat]
socktoa(rmt_addr),
On Wed, 21 Aug 2019, Hal Murray via devel wrote:
ntpd/refclock_gpsd.c has:
#define _XOPEN_SOURCE 600
I see the following warning:
NetBSD:
../../ntpd/refclock_gpsd.c:2118:6: warning: implicit declaration of function
'strlcpy' [-Wimplicit-function-declaration]
FreeBSD:
../../ntpd/refclock_gps
On Fri, 16 Aug 2019, Eric S. Raymond via devel wrote:
Sanjeev Gupta :
sizeof(double) seems to be 8 bytes. The 8192 * No of Secs per week
overflows this.
Huh. If "long double" isn't 16 bytes, we're foing to have a problem.
There's no guarantee that long double differs from double. Anythi
On Mon, 22 Jul 2019, Gary E. Miller via devel wrote:
No one has a solid answer to the NTS ALPN issue?
"at some time the NTPSEC server would return "\x07ntske/1" instead of
just "ntske/1"."
Doesn't ring any BELs for me. :-)
All kidding aside, it's probably not a coincidence that \x07 is the
On Sun, 30 Jun 2019, Mark Atwood wrote:
The NTPsec Project is pleased to announce the tagging of version 1.1.5
I guess "tagging" is a good description given that the tarball doesn't
seem to have been published. :-)
Fred Wright
___
devel mailing
On Sun, 7 Apr 2019, Hal Murray wrote:
Does a simple void cast work? E.g.:
(void) strerror_r(...)
I haven't found the magic using that approach.
../../ntpd/nts.c:214:16: warning: ignoring return value of ???strerror_r???,
declared with attribute warn_unused_result [-Wunused-result]
On Sun, 7 Apr 2019, Eric S. Raymond via devel wrote:
Hal Murray via devel :
../../ntpd/nts.c:213:9: warning: ignoring return value of ???strerror_r???,
declared with attribute warn_unused_result [-Wunused-result]
I'm only getting this on Ubuntu, so a secondary question is why isn't that
check
On Wed, 20 Mar 2019, James Browning via devel wrote:
On Wed, Mar 20, 2019 at 6:30 PM Gary E. Miller via devel
wrote:
Yo All!
Something recently broke in NTPsec when using Python 3.6:
?
I thought I got that bug with?a4453ee5a4 "Fix polyglot library for Python3 on
NetBSD".
Wher
On Mon, 11 Mar 2019, Eric S. Raymond via devel wrote:
GPSes will roll over to their third era on April 6th.
Those of us with constellations of test GPSes will need to take time
to audit how much of our kit has gone toes-up. Maybe none of it
immedately, as manufacturers tend to pivod on their
On Sun, 10 Feb 2019, Hal Murray wrote:
What's involved in getting developer access to the Mac world?
It depends on what you mean by that. There are both free and paid
developer accounts. The free version gives you access to most of the
developer downloads. That's all I've ever used. I t
1 - 100 of 165 matches
Mail list logo
