public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
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: Tue, 01 Feb 2000 16:34:00 -0000	[thread overview]
Message-ID: <38977B4E.A7EADB37@cygnus.com> (raw)
In-Reply-To: <000101bf6cbb$2ff0af10$c9a87995@drives.eurotherm.co.uk>

[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

      reply	other threads:[~2000-02-01 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-01  5:54 Robert
2000-02-01 16:34 ` Andrew Cagney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38977B4E.A7EADB37@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=robert.melchers@drives.eurotherm.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).