On Tue, Jul 11, 2017 at 03:07:24PM -0500, Jason Bacon wrote:
I think it's reasonable for an optional security feature like FORTIFY_SOURCE
to throw a warning for ignoring the return value of an I/O function that
might fail and leave a corrupted output file, so I would not say the headers
are broken.
The point is that error checking for stdio functions is normally done
using ferror() and feof(). That's exactly what fixup-libtool.c does.
Insisting on checking each call is just useless, especially since
buffering makes the error checking useless in most cases.
Joerg