Re: [PATCH] GDB command-line switches and annotations docs

[Andrew Cagney <ac131313@cygnus.com>]

Elena Zannoni wrote:
> 
> Eli Zaretskii writes:
>  >
>  > Here are patches to gdb.texinfo and annotate.texi which add indexing
>  > to command-line switches, document some switches that were not in the
>  > manual, and make annotate.texi part of GDB manual.
>  >
>  > (Are there plans to make gdbmi.texi be part of the manual as well?)
>  >
> 
> Eventually yes (Andrew?), right now it is not in prime time form yet. It is
> still very rough work in progress.

Yes its rough but still certainly better than nothing.
I guess the need to the MI commands against the doco becomes a FIXME :-(

	Andrew
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Robert <robert.melchers@drives.eurotherm.co.uk>, GDB Patches <gdb-patches@sourceware.cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: The definition for bfd_mach_sh4 is missing .
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38977B4E.A7EADB37@cygnus.com>
References: <000101bf6cbb$2ff0af10$c9a87995@drives.eurotherm.co.uk>
X-SW-Source: 2000-q1/msg00066.html
Content-length: 1004

[Technically this is a BFD problem, however, only GDB is showing it at
present]

Hi,

Can you put a note in your diary to check on this issue in about a
fortnight (two weeks).  It and a few others should be resolved next week
as part of the gdb-on-sourceware post-mortem however such issues could
be missed.

	Andrew


> Robert wrote:
> 
> The definition for bfd_mach_sh4 is missing from the file File
> bfd/bfd-in2.h the patch below corrects this allowing target = sh-coff
> to build.
> gdb/sh-tdep.c requires.
> 
> Robert.
> 
> bfd [54] diff -c3p  _bfd-in2.h bfd-in2.h
> *** _bfd-in2.h  Tue Feb 01 12:58:27 2000
> --- bfd-in2.h   Tue Feb 01 12:58:14 2000
> *************** enum bfd_architecture
> *** 1340,1345 ****
> --- 1340,1346 ----
>   #define bfd_mach_sh            0
>   #define bfd_mach_sh3        0x30
>   #define bfd_mach_sh3e       0x3e
> + #define bfd_mach_sh4        0x40
>     bfd_arch_alpha,      /* Dec Alpha */
>   #define bfd_mach_alpha_ev4  0x10
>   #define bfd_mach_alpha_ev5  0x20
From bje@redhat.com Sat Apr 01 00:00:00 2000
From: Ben Elliston <bje@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: BINUTILS Patches <binutils@sourceware.cygnus.com>, GDB Patches <gdb-patches@sourceware.cygnus.com>, Ben Elliston <bje@cygnus.com>
Subject: Re: Import of new config.guess?
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <Pine.LNX.3.95.1000210223514.6167C-100000@moshpit.cygnus.com>
References: <38A25CCD.8C8D06D1@cygnus.com>
X-SW-Source: 2000-q1/msg00111.html
Content-length: 416

> My question is easy.  What are the rules for importing this?  Only
> import official releases (is config.guess ever officially released?)

config.guess is officially released, and it's released often.  I consider
each patch to be a new release--and soon, there will be a unique verison
number to indicate this.

For the time being, you can get it via anoncvs from subversions.gnu.org in
the `config' module.

Ben