>    Also, the code seems to very buggy - my findings were triggered just by
   >    warnings from 'gcc -Wall -Wextra'. I didn't even take a closer look into
   >    the sources. Not even talking about test code coverage and fuzzing.
   >
   > Some of the code was ported from BSD 4.4-lite or something, and then
   > has been tweaked and tuned.  Some tools are written from scratch, and
   > they tend to be less buggy.  

   Observe that already Gnulib is responsible for too many warnings.
   Running clang-3.4 on FreeBSD with '-Wall -Werror' aborts in 'lib/',
   as does gcc-4.3.3 on OpenIndiana with '-Wall -Wextra -Werror',
   whereas dropping '-Wextra' lets gcc-4.3.3 enter into proper Inetutils'
   source before aborting.

   I remember complaining about this with bug-gnulib, at the time I was
   beginning to engage for Inetutils, but got answers that it be of no
   priority whatsoever. Therefor I stopped bothering about it.

Can we disable warnings from gnulib related code easily?

  • Re: inetuti... Alfred M. Szmidt
    • Re: in... Mats Erik Andersson
      • Re... Alfred M. Szmidt
        • ... Tim Rühsen
    • Re: in... simon--- via Bug reports for the GNU Internet utilities
      • Re... Alfred M. Szmidt
        • ... simon--- via Bug reports for the GNU Internet utilities
          • ... Alfred M. Szmidt
            • ... Simon Josefsson via Bug reports for the GNU Internet utilities
              • ... Alfred M. Szmidt
                • ... Simon Josefsson via Bug reports for the GNU Internet utilities
                • ... Simon Josefsson via Bug reports for the GNU Internet utilities
                • ... Alfred M. Szmidt

Reply via email to