Re: [RFA] Update gdb's configure instructions

[John Baldwin <john@baldwin.cx>]

On 9/13/18 9:29 PM, Tom Tromey wrote:
> diff --git a/gdb/README b/gdb/README
> index e43887ffcdf..d7ab18ccc6a 100644
> --- a/gdb/README
> +++ b/gdb/README
> @@ -77,8 +73,8 @@ such as:
>     If you get other compiler errors during this stage, see the `Reporting
>  Bugs' section below; there are a few known problems.
>  
> -   GDB requires an ISO C (ANSI C) compiler.  If you do not have an ISO
> -C compiler for your system, you may be able to download and install
> +   GDB requires a C++ compiler.  If you do not have a
> +C++ compiler for your system, you may be able to download and install
>  the GNU CC compiler.  It is available via anonymous FTP from the
>  directory `ftp://ftp.gnu.org/pub/gnu/gcc'.  GDB also requires an ISO
>  C standard library.  The GDB remote server, GDBserver, builds with some

I would perhaps say "C++11" compiler rather than just C++.  Also, might want
to say "GNU C++ compiler" here as I noticed you did make that update in some
other places further down.

> @@ -392,25 +388,12 @@ prefer; but you may abbreviate option names if you use `--'.
>  `--enable-build-warnings'
>       When building the GDB sources, ask the compiler to warn about any
>       code which looks even vaguely suspicious.  You should only using
> -     this feature if you're compiling with GNU CC.  It passes the
> -     following flags:
> -	-Wimplicit
> -	-Wreturn-type
> -	-Wcomment
> -	-Wtrigraphs
> -	-Wformat
> -	-Wparentheses
> -	-Wpointer-arith
> +     this feature if you're compiling with the GNU C++ compiler.  It
> +     passes many different warning flags, depending on the exact
> +     version of the compiler you are using.

In practice we seem to enable warnings on all compilers, not just GCC?
(Certainly they are enabled out-of-the-box when building with clang as cc)
  
>  `--enable-werror'
>       Treat compiler warnings as werrors.  Use this only with GCC.  It

Same is true for -Werror.

-- 
John Baldwin