Re: [gpsd-dev] Port problems in certain gpsd drivers

[Bernd Zeimetz]

Hi,

On 04/17/2012 08:31 AM, Eric S. Raymond wrote:
> I think what we're seeing here is the result of a small number of
> point bugs in the driver coding (for italk, ntrip, tsip, ublox, and
> rtcm2) that are triggered by changes in endianness or word length.

as discussed on irc I don't think that we have endian issues here as the
drivers which fail on armel (little endian arm eabi) also fail on big
endian architectures.
One issue I could imagine is that running a 32bit environment with a
64bit kernel could be an issue. If that is the case it might even be
reproucible on a normal x86_64 box running a 64bit kernel and 32bit
userland.

> If you are responsible for one of these drivers, please audit for
> unclean code.  Please communicate with Bernd Zeimetz about how to test
> your changes on the Debian porterboxes.  

As getting logins on our porterboxes is a bit complicated I would prefer
patches or even better git repositories I can pull from and even better
a short script which builds and tests what you need and I'll send you
the result.

Cheers,

Bernd

-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F