Hal Murray via devel <[email protected]>:
>
> What's the story?
>
> I'm catching up after being off line for several weeks. I updated a NetBSD
> box to 8.0 and now it produces lots and lots of warnings that I expect would
> get fixed before a release.
>
> Most are complaining about %m. Sample:
> ../../libntp/msyslog.c:512:5: warning: %m is only allowed in syslog(3) like
> functions [-Wformat=]
>
> There is also:
> ../../ntpd/ntp_control.c:2628:8: warning: format '%u' expects argument of
> type
> 'unsigned int', but argument 4 has type 'int' [-Wformat=]
>
> /usr/pkg/lib/libpython2.7.so: warning: warning: tmpnam() possibly used
> unsafely, use mkstemp() or mkdtemp()
> /usr/pkg/lib/libpython2.7.so: warning: warning: tempnam() possibly used
> unsafely, use mkstemp() or mkdtemp()
If waf detects lack of %m support in syslog(3) it does that expansion
internally.
These warnings are spurious. They mean we need to find out how to declare
to the NetBSD compiler that msyslog() is syslog-like, but that's all.
I don't consider this a release blocker.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
_______________________________________________
devel mailing list
[email protected]
http://lists.ntpsec.org/mailman/listinfo/devel
