gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why might everything but the gpsd status be unpacked?


From: Gary E. Miller
Subject: Re: Why might everything but the gpsd status be unpacked?
Date: Thu, 30 Apr 2020 11:45:20 -0700

Yo Jack!

On Thu, 30 Apr 2020 10:46:42 -0400
Jack Nadelman <address@hidden> wrote:

> Using libgps.so.25.0.0 built from gpsd-3.19.tar.gz for
> aarch64-linux-gnu embedded Linux target, why might everything but the
> status (DGPS_FIX) be unpacked to (gps_data_t) m_gps_data during the
> gps_read?

gps status is a new variable.  Try git head to see if you problem still
exists.

> nav_thread.cpp:277 (_thread_proc) - gps_bytes 270 status 0 mode 3 lat
> 26.3431 lon -80.632 alt 16.3

nav_thread.cpp is not one of the gpsd programs.  If you want someone
to look at it, send the entire file and instructions to build it.

> scons minimal=yes shared=True gpsd=False gpsdclients=False
> socket_export=yes clientdebug=yes
>     target='aarch64-linux-gnu'

Minimal is a bad idea.  But without knowing your use case, hard to say
exactly why.

> I am able to work around the issue by parsing the status from the
> message returned by gps_read and using that to set the gps_data_t
> status field like this

Which ignores most of the possible STATUS_ values.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgp0qGw5W5BnS.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]