Re: ✘gcc 8.2.0 warnings

2018-08-30 Thread Gary E. Miller via devel
Yo Matthew! > > On Fri, 31 Aug 2018 01:35:14 + > Matthew Selsky wrote: > > > On Thu, Aug 30, 2018 at 06:21:49PM -0700, Gary E. Miller via devel > > wrote: > > > > > I recently updated to gcc 8.2.0. Of course it leads to new > > > warnings. > > > > Any idea why our gcc 8.2.0 CI job h

Re: ✘gcc 8.2.0 warnings

2018-08-30 Thread Gary E. Miller via devel
Yo Matthew! On Fri, 31 Aug 2018 01:35:14 + Matthew Selsky wrote: > On Thu, Aug 30, 2018 at 06:21:49PM -0700, Gary E. Miller via devel > wrote: > > > I recently updated to gcc 8.2.0. Of course it leads to new > > warnings. > > Any idea why our gcc 8.2.0 CI job has no such warnings? See

Re: ✘gcc 8.2.0 warnings

2018-08-30 Thread Matthew Selsky via devel
On Thu, Aug 30, 2018 at 06:21:49PM -0700, Gary E. Miller via devel wrote: > I recently updated to gcc 8.2.0. Of course it leads to new warnings. Any idea why our gcc 8.2.0 CI job has no such warnings? See https://gitlab.com/NTPsec/ntpsec/-/jobs/93445599 How are you calling waf configure? Any

✘gcc 8.2.0 warnings

2018-08-30 Thread Gary E. Miller via devel
Yo All! I recently updated to gcc 8.2.0. Of course it leads to new warnings. [ 80/135] Compiling ntpd/refclock_pps.c ../../ntpd/refclock_trimble.c:179:2: warning: initialization of 'void (*)(int, struct refclockproc *)' from incompatible pointer type 'void (*)(int, struct peer *)' [-Wincompa