On Thu, Feb 03, 2005 at 03:31:25PM -0600, Robert Lipe wrote: > John Goerzen wrote: > > > 've received some more information about failures to build gpsbabel. > > Kurt Roeckx provided some helpful data. > > It's not entirely clear which version of GPSBabel is in question here.
Sorry. It's 1.2.4. > > What can we do to help you debug the problem? > > Can you provide an account on failing systems and/or someone able & > willing to drive a debugger. I don't think accounts are available, but I can probably drive a debugger on most of these archs for you. > > > On sparc: > > > ./testo > > > 2,1142c2,1142 > > > < 37.004356, -5.549169, 519.25, 09/05/03 14:34:08, 1 > > > > 37.004356, -5.549169, 519.25, 09/05/03 15:34:08, 1 > > This looks like a timezone problem I fixed in psitrext back in Oct of 03 > but it might be needed the 'FREEZE_TIME' fix I applied in April of 04. Hmm, would that have escaped 1.2.4 somehow? > > > On alpha, amd64: > > There's an alpha/debian system on compilefarm.sf.net. I just checked > out the top of the tree and ran > > make LIBUSB= INHIBIT_USB=-DNO_USB > > (Apparently this system doesn't have libusb installed) Hmm, the main Makefile I'm using already lists: INHIBIT_USB=-DNO_USB However, we do have libusb on Debian so I could enable USB for all archs. (No USB deps were specified in our Debian build system, which could be why inconsistent results are being produced wrt USB.) > > > > ./testo > > > 8a9,4969 > > > > <rte> > > > > <rtept lat="35.824742" lon="-86.850357"> > > > > <name>\00000</name> > > > > </rtept> > > With access to an alpha, I see that problem and have a preliminary fix > in hand. Give me a day or two for an Official Fix. Super! > For discussions sake, is <stdint.h> (yes, I know it's technically a > C99-ism) considered fair game in the world of portability now? Looks like it's been part of GCC since 1997, so it should be quite portable to Unix/Linux platforms. > > > And on arm: [snip] > > This is something in the MXF format. I don't see that on Alpha. My gut > tells me it's another silly sizeof(something) problem. I know that arm is weird in some respect wrt floating-point, but I don't know a whole lot about it. I think though that sizeof(whatever) there is pretty similar to i386, where it builds fine. Thanks for your assistance! -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
