Hal Murray :
> How does that work?
>
> On Linux, it's in:
> /usr/include/python2.7/Python.h
> but the code does:
> #include
>
> On NetBSD, it's in:
> /usr/pkg/include/python2.7/Python.h
>
> On FreeBSD, it's in:
> /usr/local/include/python2.7/Python.h
What the build system is expected t
How does that work?
On Linux, it's in:
/usr/include/python2.7/Python.h
but the code does:
#include
On NetBSD, it's in:
/usr/pkg/include/python2.7/Python.h
On FreeBSD, it's in:
/usr/local/include/python2.7/Python.h
--
These are my opinions. I hate spam.
___
Yo Eric!
On Sat, 22 Oct 2016 09:21:59 -0400
"Eric S. Raymond" wrote:
> Hal Murray :
> > >> I assume that using a pipe or socket rather than SHM would fix
> > >> that.
> >
> > > Probably, but then we run unto buffering jitter again.
> >
> > Are we on the same wavelength yet? Have we agre
Yo Hal!
On Sat, 22 Oct 2016 03:15:01 -0700
Hal Murray wrote:
> >> Word-length mismatch between two programs built under the same OS
> >> never happens, or close enough to never that I don't care.
> > Uh, no. remember when intel OS went from 32 bit to 64-bit? It was
> > a huge issue with ntpd
Yo Hal!
On Sat, 22 Oct 2016 02:31:01 -0700
Hal Murray wrote:
> >> I assume that using a pipe or socket rather than SHM would fix
> >> that.
>
> > Probably, but then we run unto buffering jitter again.
>
> Are we on the same wavelength yet? Have we agreed that latency is
> not critical? I
> What ntpd gets from a clock source is a series of pairs asserting "at system
> time X I believe it was UTC time Y".
Right.
> Are you telling me there is no value in minimizing the time from X to when
> the sample triggers a correction, and the variation in that time?
> Basic servocontrol theo
I discovered my Jenkins system hasn't been triggering builds on SCM
changes since the 18th.
Somewhere in the big changeset listed below, RHEL/Cent 6 got broken again.
(Sorry for the links to localhost in the output.)
CentOS 7 and Fedora 24 are still building OK, as is Ubuntu 14 and 16.
Hal Murray :
> >> I assume that using a pipe or socket rather than SHM would fix that.
>
> > Probably, but then we run unto buffering jitter again.
>
> Are we on the same wavelength yet? Have we agreed that latency is not
> critical? If so, why is jitter important?
It is possible that I am co
>> I assume that using a pipe or socket rather than SHM would fix that.
> Probably, but then we run unto buffering jitter again.
Are we on the same wavelength yet? Have we agreed that latency is not
critical? If so, why is jitter important?
--
These are my opinions. I hate spam.
>> Word-length mismatch between two programs built under the same OS
>> never happens, or close enough to never that I don't care.
> Uh, no. remember when intel OS went from 32 bit to 64-bit? It was a huge
> issue with ntpd. RasPi is about to have the same problems.
What sort of problem do yo
10 matches
Mail list logo