On 03/13/2018 09:54 AM, Reuben Thomas wrote:
I see you seem to have put a similar pragma for the same warning in anytostr.c.

Yes, and that's the sort of thing I'd rather not do elsewhere. That mess started with the thread here:

https://lists.gnu.org/r/bug-gnulib/2010-10/msg00428.html

how about changing manywarnings to use suitable flags for gnulib code? (Though I can see potential problems with that too…

Something that coreutils etc. could use, instead of the by-hand stuff they do nowadays? That would be nice, I think. Not quite sure how to do it, though.


Reply via email to