Re: NTPsec on MIPSbe

I just finished testing the refclocks supported by the Trimble driver on a sparc64 machine. The configure was able to set WORDS_BIGENDIAN 1 without any problem. I didn't notice any runtime problems besides what's likely due to serial port delays, but there were some warnings during the

Re: NTPsec on MIPSbe

On Wed, May 24, 2017 at 3:23 AM, Matthew Selsky via devel wrote: > > Sanjeev/Hal, > > Did waf's endian-ness test not detect this properly? It worked perfectly, no manual intervention or extra parameters required. -- Sanjeev Gupta +65 98551208

Re: waf, git, EPOCH, version strings, ...

Yo Hal! On Tue, 23 May 2017 13:56:07 -0700 Hal Murray wrote: > >> configure sets up NTPSEC_VERSION_STRING > >> ntptime is the only useage. > > Seems like a different issue than detecting an old or unusable > > configure. Do you propose a tie-in? > > Only that the

DNS testing - name that won't respond

Is there a handy name that can be used to generate EAI_AGAIN? I think that only happens if the server doesn't respond? -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: waf, git, EPOCH, version strings, ...

There may be some confusion between comments about what exists and what I'd like. > Yes. People forgetting to run configure is a persistent problem. Eric: An item for your list. I don't have any good suggestions for how to fix that. I think it could also happen if a tarball was extracted

Re: NTPsec on MIPSbe

>> #define WORDS_BIGENDIAN 1 >Did waf's endian-ness test not detect this properly? waf's detection worked fine. The above #define is from config.h on a PowerPC indicating what it did. - > ISTR years ago seeing some C magic, where in a compile time declaration, one > packs bytes into a

Re: NTPsec on MIPSbe

On Tue, May 23, 2017 at 11:59:24AM -0700, Hal Murray via devel wrote: > If you are keeping track... > > It builds and runs on a 32 bit PowerPC MAC-Mini, both Debian and FreeBSD. > > #define WORDS_BIGENDIAN 1 > > There are problems with the firmware setting up the time keeping parameters >

Re: NTPsec on MIPSbe

If you are keeping track... It builds and runs on a 32 bit PowerPC MAC-Mini, both Debian and FreeBSD. #define WORDS_BIGENDIAN 1 There are problems with the firmware setting up the time keeping parameters incorrectly. I can patch it via Open Firmware, but haven't figured out how to make it

Re: NTPsec on MIPSbe

Thanks! On Mon, May 22, 2017 at 2:32 AM Sanjeev Gupta via devel wrote: > After a fruitless two months trying to find a big endian machine, I > finally booted a qemu instance. > > Running Debian 7, 256M RAM, 32 bit. gcc 4.6, kernel 3.2 > > buildprep fails because Debian 7 did

Re: waf, git, EPOCH, version strings, ...

Yo Hal! On Mon, 22 May 2017 23:26:05 -0700 Hal Murray via devel wrote: > I think the tangle mentioned at Issue #313 needs wider discussion. > ntpsec | build version not updated after git pull (#313) > https://gitlab.com/NTPsec/ntpsec/issues/313 Yes. People forgetting to

waf, git, EPOCH, version strings, ...

I think the tangle mentioned at Issue #313 needs wider discussion. ntpsec | build version not updated after git pull (#313) https://gitlab.com/NTPsec/ntpsec/issues/313 A while ago, we changed things to not use __DATE__. Maybe we didn't get that right. Maybe the default should be to use