Hello Gary.
> > Before we can help you furhter, you need to run gpsdebuginfo, and
> > send us the output. That is easier for us all, rather than playing
> > 20 questions to get the important info from you that you have not
> > already provided.
> >
>
> That's not an option because gpsd is running on a proprietal embedded
> system without many tools gpsdebuginfo uses, e.g. python. So the
> output is full of "command not found" messages, not useful.
Please let be the judge of what is useful. A lot of the output
does not require python. None of the stuff I was looking for
from you needed python.
OK, gpsdebuginfo output attached.
> #if defined(CONTROL_SOCKET_ENABLE) && defined(SOCKET_EXPORT_ENABLE)
tell me you did not compile so that this part did not get built?
As I want the gpsd binary to be as low in size as possible and no clients to be build, I used following flags.
scons -j 8 minimal=True manbuild=False gpsdclients=False ublox=True socket_export=True nostrip=True prefix=''
I thought the control socket is not needed to compile if not used. But then the PPS messages were not be shipped. After adding control_socket=True they started coming.
> /* on PPS interrupt, ship a message to all clients
With no sockets, no way for gpsd to ouput the time!
There is the TCP socket for clients to connect. And SHM blocks for NTP synchronization.
Can you send me your build log? Looks like you have done so weird things.
Yes, the build is definitely not standard. I cross-compile in a proprietary build system. I attach the build log.
Many thanks
Tomáš
build.log