I was setting up ntpsec on a Raspberry Pi. Things got confused. It looked
like another instance of the drift stuck at 500 ppm bug, issue 44
https://gitlab.com/NTPsec/ntpsec/issues/44
but things got even more confused when I tried to gather more info.
I finally figured out that systemd-timesy
> > '-DPYTHONDIR="/usr/local/lib/python2.7/site-packages"',
> > '-DPYTHONARCHDIR="/usr/local/lib64/python2.7/site-packages"',
> > '-DHAVE_PYEXT=1', '-DHAVE_PYTHON_H=1'
> Yeah, that's boilerplate for use by Python extensions written in C.
I haven't found any uses in our code. Should we remove it
Hal Murray :
> > What's mysterious here?
>
> I haven't figured out what this stuff is doing. I don't think any of them
> are referenced by any of the code.
>
> > '-DPYTHONDIR="/usr/local/lib/python2.7/site-packages"',
> > '-DPYTHONARCHDIR="/usr/local/lib64/python2.7/site-packages"',
> > '-DHA
On Fri, Nov 24, 2017 at 06:44:29AM -0500, Eric S. Raymond via devel wrote:
> Hal Murray via devel :
> > I can't figure out what it is trying to tell me. There is no "local" in my
> > script. It works on my CentOS 6 system. Note that it is git complaining.
> > My script does waf builds, no git
> ?? I haven't figured out how the simple case builds without warnings.
Found it.
My script that generates warnings nukes the build directory.
Running configure again, then build, recompiles lots of stuff, but not
everything. I'm guessing it notices the new config.h which timespecops.c
doesn'
> What's mysterious here?
I haven't figured out what this stuff is doing. I don't think any of them
are referenced by any of the code.
> '-DPYTHONDIR="/usr/local/lib/python2.7/site-packages"',
> '-DPYTHONARCHDIR="/usr/local/lib64/python2.7/site-packages"',
> '-DHAVE_PYEXT=1', '-DHAVE_PYTHON_H
Hal Murray :
> More poking around... Remember, I don't really grok waf.
>
> The call to write_config_header has a suspicious looking argument. So I
> tried it.
> -ctx.write_config_header("config.h", remove=False)
> +ctx.write_config_header("config.h", remove=True)
>
> config.h looks re
More poking around... Remember, I don't really grok waf.
The call to write_config_header has a suspicious looking argument. So I
tried it.
-ctx.write_config_header("config.h", remove=False)
+ctx.write_config_header("config.h", remove=True)
config.h looks reasonable. waf -v is much les
Hal Murray :
> devel@ntpsec.org said:
> > waf doesn't know that config.h exists; this is its way to pass configuration
> > switches. The fact that we generate a config.h is really legacy behavior
> > from autoconf and could be eliminated, but it's low on my priority list.
>
> It may be "legacy",
devel@ntpsec.org said:
> waf doesn't know that config.h exists; this is its way to pass configuration
> switches. The fact that we generate a config.h is really legacy behavior
> from autoconf and could be eliminated, but it's low on my priority list.
It may be "legacy", but I like it. It's a h
Hal Murray via devel :
>
> The output from waf -v is full of crap like this:
>
> -DHAVE_STRUCT_TIMEX=1', '-DHAVE_STRUCT_NTPTIMEVAL=1',
> '-DHAVE_STRUCT_TIMEX_MODES=1', '-DHAVE_STRUCT_NTPTIMEVAL_TAI=1',
> '-DNTP_SIZEOF_LONG=4', '-DNTP_SIZEOF_TIME_T=4', '-DOPEN_BCAST_SOCKET=1',
> '-DHAVE_OPENSSL
On Fri, Nov 24, 2017 at 2:51 AM, Hal Murray via devel wrote:
> Did this work before my change? Is somebody working on the gitlab stuff and
> my push just happened at the right time to uncover a bug?
I suspect this was a transient CI error or possibly related to work
Matt was doing at that time
k...@roeckx.be said:
> This means that when we initialize a global variable we use the
> pthread_once() function, which internally uses the futex to do that. It's
> not using threads itself, it's just making sure that if you use threads
> things work properly.
Thanks.
Do we have to link with pt
An interesting tangle. I'm cleaning up odds and ends, including upgrading
Raspberry Pi-s to Stretch. One of them dies with a SIGSYS trap.
It's dieing on 240 which is futex. That's locks, only needed if you are
using threads. This system was built with --disable_dns_lookup, so there
shouldn'
The output from waf -v is full of crap like this:
-DHAVE_STRUCT_TIMEX=1', '-DHAVE_STRUCT_NTPTIMEVAL=1',
'-DHAVE_STRUCT_TIMEX_MODES=1', '-DHAVE_STRUCT_NTPTIMEVAL_TAI=1',
'-DNTP_SIZEOF_LONG=4', '-DNTP_SIZEOF_TIME_T=4', '-DOPEN_BCAST_SOCKET=1',
'-DHAVE_OPENSSL_EVP_H=1', '-DHAVE_OPENSSL_RAND_H=1',
It seems like a good idea for somebody to actually test our code on a
big-endian system.
I have a Mac Mini G4. It's currently running Debian 8/jessie. But Debian
9/stretch has dropped support for powerpc.
Does anybody know of Linux distros that support 32 bit PowerPC? I want to
download a
16 matches
Mail list logo
