Build Broken for RHEL/Cent 6 - undefined reference to `clock_settime'

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.

Re: Proposal - drop the GPSD JSON driver

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?

Re: Proposal - drop the GPSD JSON driver

>> 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

Re: Proposal - drop the GPSD JSON driver

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

Re: Proposal - drop the GPSD JSON driver

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

Re: Proposal - drop the GPSD JSON driver

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

Re: Python.h is broken on NetBSD and FreeBSD

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

Python.h is broken on NetBSD and FreeBSD

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.