[INSTALL] Update concerning MinGW and the __USE_MINGW_ANSI_STDIO macro.

The change done in r13668 seems to be a bit wrong (at least unclear),
since there are several compliance issues with printf(), and it seems
that this has completely been resolved only recently, in version 8.
http://mingw-w64.org/doku.php says:
  Version 8 has been released
  v8.0.0: 2020-09-18
  Notable changes:
  [...]
    * __USE_MINGW_ANSI_STDIO now automatically enabled in C99 and C11
      mode when not using UCRT by Pali Rohár
  [...]

Compiling
  #include <stdio.h>
  int main (void) { volatile double d = -1.25; printf ("%e\n", d); }
gives with mingw-w64 version 7: -1.250000e+000
  and with mingw-w64 version 8: -1.250000e+00

So, when testing MPFR with mingw-w64 version 8 but with GMP still built
with mingw-w64 version 7 (and static libraries), one gets a failure in
tsprintf:
  Error in mpfr_vsprintf (s, "%e", ...);
  expected: "-1.250000e+00"
  got:      "-1.250000e+000"
because the expected result has changed (it comes from sprintf used in
the MPFR test, which is now ISO-compliant).

git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14137 280ebfd0-de03-0410-8827-d642c229c3f4

1 files changed, 2 insertions, 3 deletions

diff --git a/INSTALL b/INSTALL
index e3966bcaa..a1d516bb0 100644
--- a/INSTALL
+++ b/INSTALL
@@ -618,10 +618,9 @@ a. Using MinGW
 3 - To avoid using the Microsoft runtime (which might not be conform to ISO C),
     you can use the MinGW runtime package (which is an integral part of MinGW).
 
-    With old MinGW versions, you can get an ISO-compliant printf()
+    With MinGW versions before 8, you can get an ISO-compliant printf()
     if you compile your application with either '-ansi', '-posix' or
-    '-D__USE_MINGW_ANSI_STDIO'. But note that this latter option,
-    which was useful in the past (see below) should no longer be used.
+    '-D__USE_MINGW_ANSI_STDIO'.
 
     The following applies to old MinGW versions, and may be discouraged
     with recent MinGW versions.