Fred Wright via devel :
> The failure is gone at the current master (8e7e0677d).
Good to know. I was a little worried about this while on the road this
weekend.
> I assume that "xurrebt" is a bottom-row-shifted version of "current". :-)
Right. I can spell, but my typing is terrible. :-)
--
Yo Matthew!
On Sat, 2 Sep 2017 21:28:20 -0400
Matthew Selsky via devel wrote:
> Are there extra options we should pass to ./waf configure to catch
> these types of errors in our gitlab bots?
Here is my formula:
./waf configure --enable-debug --enable-debug-gdb --enable-warnings \
--refclock=a
Hey Eric/Gary:
Are there extra options we should pass to ./waf configure to catch these types
of errors in our gitlab bots?
I'm happy to update our .gitlab-ci.yml to do extra checking so we detect these
before users do.
Thanks,
-Matt
___
devel mailin
On Fri, 1 Sep 2017, Eric S. Raymond via devel wrote:
> Gary E. Miller via devel :
> > 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 ex
Gary E. Miller via devel :
> 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
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
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
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
---
12 matches
Mail list logo
