Re: Build Errors with Timeservice + Ubuntu 16.04

[Dan Williams]

Yo Gary, I've adjusted the build parameters as you suggested; results are below. (I won't comment on the documentation, until I understand more)

> Why are you building detached HEAD?  If you are pulling git, then
> use all the bug fixes in git HEAD.  Especially if you use a u-blox
> 9-series.

Both branches have the same result -- but to answer your question: I built off the release, because releases are often more stable than nightlies.

I've checked out 'master', and will build off that, from now on.

> What is your receiver?
 
An OxTS RT-3000.
https://www.oxts.com/products/rt3000/

It's relatively high-end, but I'm not able to figure out what chip it uses.

We have it configured to send:
- GPGGA @ 10hz
- GPRMC @ 1hz
- GPZDA @ 10hz
- GPGSA @ 1hz

> > In that case, what's the "default" flags to enable PPS + shm + time
> > reporting?
>
> That default is:
>         scons -c && scons && scons install
>

Okay, clearly I went down the wrong path.  Rather than get sidetracked, let's just talk about the right path.

It sounds like you're saying that PPS should be enabled with a plain scons build, yes?  And that plain build, will be sending PPS signals?  

That is the intended behavior?  Do I understand that correctly?


>
> How do you start gpsd?
>
> While gpsd is running, send the results of these three items, as root,
> not sudo:
>
>     # pstree -paul | fgrep gpsd
>     # netstat -apn | fgrep 2947
>     # gpspipe -w -n 30


Okay, Second Try:

1) Build
> $ scons && scons check
     - note:  I get the same results when I add "--config=force ntpshm=yes pps=yes")

     - this DOES pass the checks, but doesn't send any PPS messages.

2) gpsd Invocation
> $ stty -F /dev/ttyS6 115200 && ./gpsd -bn /dev/ttyS6                                                                                                                                                                                          
    - you may notice that I'm just running it from the build directory, for now.

3) pstree output
> root@gt104:/opt/gpsd# pstree -paul | grep gpsd
>  |-gpsd,9616,dwilliams -bn /dev/ttyS6
>  |   `-{gpsd},9619
>  |   |                       |-grep,9696 --color=auto gpsd

4) netstat
> root@gt104:/opt/gpsd# netstat -apn | fgrep 2947
> tcp        0      0 127.0.0.1:2947          0.0.0.0:*               LISTEN      9616/gpsd      
> tcp6       0      0 ::1:2947                :::*                    LISTEN      9616/gpsd  

Which we know, because cgps and gpsmon, etc show output.

5) gpspipe output
(attached in 'gpspipe.log')
- includes both input-nmea and output-json
- Note the missing PPS json messages.

- gpsmon agrees, and merely shows "PPS: N/A"

gpsd-build.txt
Description: Text document

gpspipe.log
Description: Text Data