Yo Eric!
On Thu, 31 Aug 2017 23:35:03 -0400
"Eric S. Raymond via devel" wrote:
> > Expected 3486372600 Was 104913720
Sure looks like integer overflow.
> Something about the expression "(int32_t)*yearstart + tmp" is
> computing differently under MacOS than elsewhere. Anyone got any
> ideas?
y
Yo Eric!
On Thu, 31 Aug 2017 22:41:04 -0400
"Eric S. Raymond" wrote:
> Gary E. Miller via devel :
> > I just tried to build ntpsec for the first time in weeks. Not
> > good.
>
> Were you formerly getting these?
Yes, I see no way to fix ntp_parser_tab.c. That is why the sign conversion
warn
Yo Hal!
On Thu, 31 Aug 2017 21:07:51 -0700
Hal Murray via devel wrote:
> Is there a buildbot? Does it work? What OSes and options does it
> try? I haven't seen mail from it in ages.
It sends IRC messages to #ntpsec-dev. You should also have a loging
to https://buildbot.ntpsec.org/
RGDS
GAR
> Aha. With *that* I can reproduce these - don't get them with my normal
> invocation.
What was interesting about Gary's recipe that you didn't normally test?
Is there some option that we should add to tests/option-tester.sh?
Does anybody use it?
Is there a buildbot? Does it work? What OSe
Fred Wright via devel :
> Here I don't see build failures (admittedly without all Gary's options),
> but I do see a test failure (OSX):
>
> TEST(clocktime, CurrentYearExplicit)../../tests/libntp/clocktime.c:59::FAIL:
> Expected 3486372600 Was 104913720
>
> This bisects to commit 5489ed5a593c8e14
On Thu, 31 Aug 2017, Eric S. Raymond via devel wrote:
> Gary E. Miller via devel :
> > I just tried to build ntpsec for the first time in weeks. Not good.
>
> Were you formerly getting these?
>
> ntp_parser.tab.c: In function ‘yytnamerr’:
> ntp_parser.tab.c:1329:21: warning: conversion to ‘long
It's not necessary to use refclock_process() if the driver creates
its own l_fp timecode timestamp and uses refclock_process_offset(). I
was considering removing refclock_process() when I added the rollover
workaround to the trimble driver, but then I read this:
https://bugs.ntp.org/show_bu
Gary E. Miller via devel :
> I just tried to build ntpsec for the first time in weeks. Not good.
Were you formerly getting these?
ntp_parser.tab.c: In function ‘yytnamerr’:
ntp_parser.tab.c:1329:21: warning: conversion to ‘long unsigned int’ from ‘long
int’ may change the sign of the result [-W
Gary E. Miller via devel :
> > I just tried to build ntpsec for the first time in weeks. Not good.
>
> Here is how I build:
>
> ./waf configure --enable-debug --enable-debug-gdb --enable-warnings \
> --refclock=all --enable-doc --enable-seccomp && \
> ./waf build && \
> ./waf install
Aha.
Yo Gary!
> I just tried to build ntpsec for the first time in weeks. Not good.
Here is how I build:
./waf configure --enable-debug --enable-debug-gdb --enable-warnings \
--refclock=all --enable-doc --enable-seccomp && \
./waf build && \
./waf install
RGDS
GARY
---
Yo All!
I just tried to build ntpsec for the first time in weeks. Not good.
See attached.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Hal Murray :
>
> >> We could test fixup software by setting the system clock
> >> ahead far enough to look like GPS had rolled over.
>
> > What kind of fixup? I looked long and hard at this problem in the context
> > of GPSD. I never found one that wasn't as bad - or worse - than relying on
> >
12 matches
Mail list logo
