Gary said:
> It compiles fine, until I add this:
> export CFLAGS="-Wvla -fanalyzer"
Apologies for the noise and/or not paying attention sooner and thanks for
opening up this can of worms.
In case anybody else hasn't looked in the man page yet...
-Wvla
Warn if a variable
Yo Hal!
On Sat, 06 Nov 2021 16:07:20 -0700
Hal Murray wrote:
> > BUg or not, gcc should compile NTPsec.
> Where did you get the version you are using? Can you double check
> the download and install?
I tried this on different host: Gentoo unstable on amd64.
gcc version:
# gcc-config -l
[
Yo Hal!
On Sat, 06 Nov 2021 16:07:20 -0700
Hal Murray wrote:
> > BUg or not, gcc should compile NTPsec.
>
> Not if you have a broken version of gcc.
My gcc is not broken. I recently recompiled the world with it.
> We've done a very good job of fixing warnings. Other than the one
> from th
> BUg or not, gcc should compile NTPsec.
Not if you have a broken version of gcc.
We've done a very good job of fixing warnings. Other than the one from the
old versions of Bison, I haven't seen any warnings in a long time.
Where did you get the version you are using? Can you double check the
Yo Hal!
On Tue, 02 Nov 2021 21:15:25 -0700
Hal Murray wrote:
> Looks like a compiler bug to me. But that's just a quick look.
BUg or not, gcc should compile NTPsec.
> Are you using some non-standard compiler options?
Dunno, I'll test.ZZ
./waf -vvv configure --enable-debug --enable-debug-gdb
Looks like a compiler bug to me. But that's just a quick look.
Are you using some non-standard compiler options? Does it get the same errors
on a different architecture?
The first one is in libntp/authkeys.c so I should be familiar with that code.
It's complaining about the second line in t
