simon-git: putty (pre-0.75): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  f3ee4dbe Remove -Werror from all the default cflags.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: pre-0.75
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2021-04-27 18:18:29

commit f3ee4dbe20cc935edc78d2fcdd37c24130f62e86
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=f3ee4dbe20cc935edc78d2fcdd37c24130f62e86;hp=17371e0df05ccf57f858b852b8bec632ac889a18
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue Apr 27 17:58:28 2021 +0100

    Remove -Werror from all the default cflags.
    
    I've recently been coming round in general to the idea that -Werror is
    fine for developers and centralised binary builds, but has too many
    unanticipated failure modes in the field (with everyone's different
    versions of compilers, headers etc) to leave turned on for the 'just
    download and build' source tarball that's supposed to work everywhere.
    On main, I've already made the change to hide it behind a cmake
    'strict' setting.
    
    In particular, I've just done pre-release build tests with various
    versions of GTK, which reminded me that the GTK 2 installation on
    Ubuntu 20.04 fails to build at -Werror, because GTK's own header files
    have a warning-generating inconsistency. (glib/gtypes.h declares
    GTimeVal as deprecated, and then gtk/gtktooltips.h uses it anyway.)
    Clearly this is the kind of thing that ought not to break the build of
    a client application!

 configure.ac | 4 ++--
 mkfiles.pl   | 8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)