Yo Hal!
On Fri, 14 Apr 2017 11:59:56 -0700
Hal Murray wrote:
> > Then how did you last commit, which failed to build with
> > --enable-debug slip through?
>
> It used to be the default. My setup hasn't yet recovered from that
> switch.
Yeah, it will take a while for everyone to catch up.
>
> Then how did you last commit, which failed to build with --enable-debug slip
> through?
It used to be the default. My setup hasn't yet recovered from that switch.
Why didn't buildbot complain?
> I test with both (usually) before pushing.
Is that a run time test, or just a build?
We need m
Yo Hal!
On Fri, 14 Apr 2017 02:57:07 -0700
Hal Murray wrote:
> > Warnings, not errors.
>
> Weird. I thought of that several seconds after sending the message.
A good reason not to email at 3am. :-)
> > You should only get those if you have --enable-debug
>
> That's my default setup.
T
> Warnings, not errors.
Weird. I thought of that several seconds after sending the message.
> You should only get those if you have --enable-debug
That's my default setup.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntp
Yo Hal!
On Thu, 13 Apr 2017 23:27:03 -0700
Hal Murray wrote:
> I assume that is work in progress rather than something I did.
Warnings, not errors.
You should only get those if you have --enable-debug
I started out with over a thousand, now just over 100 hundred left to
fix.
Feel free to fix
I assume that is work in progress rather than something I did.
samples:
test-all/test.log:../../libisc/error.c:28:50: warning: initialization
left-hand side might be a candidate for a format attribute
[-Wsuggest-attribute=format]
test-all/test.log:../../libisc/error.c:29:45: warning: initializat