Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=40996.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-09-18T23:20:33+00:00 orbisvicis wrote:

log:

geoclue-gpsd.c:43:27: error: ‘gps_data’ redeclared as different kind of symbol
/usr/include/gps.h:1713:35: note: previous declaration of ‘gps_data’ was here
geoclue-gpsd.c: In function ‘geoclue_gpsd_start_gpsd’:
geoclue-gpsd.c:400:2: error: too few arguments to function ‘gps_open’
/usr/include/gps.h:1705:12: note: declared here
geoclue-gpsd.c:402:57: error: ‘POLL_NONBLOCK’ undeclared (first use in this 
function)
geoclue-gpsd.c:402:57: note: each undeclared identifier is reported only once 
for each function it appears in
geoclue-gpsd.c:403:3: error: implicit declaration of function 
‘gps_set_raw_hook’ [-Werror=implicit-function-declaratio
geoclue-gpsd.c: In function ‘gpsd_poll’:
geoclue-gpsd.c:416:3: error: implicit declaration of function ‘gps_poll’ 
[-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors


packages:

gcc 4.6.1
gpsd 3.1.1
geoclue-git
Linux 3.0-ARCH i686


other:

I spoke to li...@irc.freenode.net/gpsd who suggested the implementation 
http://lindi.iki.fi/lindi/gpsd/gpsd-test3.c might be better than parsing nmea 
strings (though there might be a reason to insist on nmea)
... (geoclue-gpsd.c)
gps_stream(self->gpsdata, WATCH_ENABLE | WATCH_NMEA | POLL_NONBLOCK, NULL);
gps_set_raw_hook (self->gpsdata, gpsd_raw_hook);
...
Whatever the case, fixing this is probably more complex than drop-in 
replacements, so filing here.

Reply at: https://bugs.launchpad.net/geoclue/+bug/893310/comments/0

------------------------------------------------------------------------
On 2011-11-19T11:44:15+00:00 Bernd Zeimetz wrote:

Parsing NMEA strings is definitely the wrong way. IMHO the whole gpsd
provider needs to be rewritten from scratch.

lindi's implementation is not uptodate for API v5 anymore, too. gps_poll
is gone for good.

Reply at: https://bugs.launchpad.net/geoclue/+bug/893310/comments/1

------------------------------------------------------------------------
On 2011-12-14T11:47:11+00:00 James Page wrote:

Created attachment 54418
Transition to use of new libgps API

I hit this bug whilst transitioning packages to the new libgps API.

The attached patch refactors the codebase to support the new API whilst
maintaining backwards compatibility.

Reply at: https://bugs.launchpad.net/geoclue/+bug/893310/comments/3


** Changed in: geoclue
       Status: Unknown => Confirmed

** Changed in: geoclue
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893310

Title:
  geoclue: will fail to build against gpsd 3.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/geoclue/+bug/893310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to