Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: Breakage on builder RHEL-s390x-m64, revision c2bf1eecf99abc4d546bb52a008a25e64a29d85e
Date: Mon, 16 Apr 2018 11:23:00 -0000	[thread overview]
Message-ID: <20180416112251.GU3684@bubble.grove.modra.org> (raw)
In-Reply-To: <E1f81q2-00034Z-Tk@kwanyin.sergiodj.net>

On Mon, Apr 16, 2018 at 06:58:22AM -0400, gdb-buildbot@sergiodj.net wrote:
> Unfortunately it seems that there is a breakage on GDB.
> 
> Commit title: 'Remove m88k support'
> Revision: c2bf1eecf99abc4d546bb52a008a25e64a29d85e
[snip]
> ../../binutils-gdb/gdb/m88k-tdep.c: In function void _initialize_m88k_tdep():
> ../../binutils-gdb/gdb/m88k-tdep.c:867:21: error: bfd_arch_m88k was not declared in this scope
>    gdbarch_register (bfd_arch_m88k, m88k_gdbarch_init, NULL);

Yes, removing the bfd support for m88k will do that..

m88k has been obsolete since 2016-09-27, ie. it was obsolete in
binutils-2.28 and should have been removed for binutils-2.29.

sparc-aout and sparc-coff, m68k-aout and m68k-coff, sh5 and sh64,
sh-symbianelf, vax-bsd and vax-ultrix, w65, we32k, m88k, h8500,
h8300-coff, ieee695, tandem, newsos3, netware, and tahoe all
went today.

i860, i960, bout, adobe and icoff targets disappeared last week.

-- 
Alan Modra
Australia Development Lab, IBM


  reply	other threads:[~2018-04-16 11:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c2bf1eecf99abc4d546bb52a008a25e64a29d85e-master-breakage@gdb-build>
2018-04-16 10:58 ` gdb-buildbot
2018-04-16 11:23   ` Alan Modra [this message]
2018-04-16 11:37     ` Pedro Alves
2018-04-16 12:19       ` [pushed] gdb: Remove OpenBSD/m88k support (Re: Breakage on builder RHEL-s390x-m64, revision c2bf1eecf99abc4d546bb52a008a25e64a29d85e) Pedro Alves
2018-04-16 12:41         ` [pushed] gdb: Remove support for SH-5/SH64 " Pedro Alves
2018-04-16 14:08     ` h8300/ecoff " Pedro Alves
2018-07-11 19:48       ` [pushed] gdb: Remove traces of h8300 ecoff support Pedro Alves
2018-04-16 11:06 ` Breakage on builder Fedora-s390x-m64, revision c2bf1eecf99abc4d546bb52a008a25e64a29d85e gdb-buildbot
2018-04-16 12:56 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-04-16 12:58 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-04-16 13:01 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2018-04-16 13:02 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-04-16 13:02 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-04-16 13:03 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2018-04-16 13:22 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-04-16 15:25 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2018-04-16 15:27 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2018-04-16 15:28 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-04-17  0:57 ` Breakage on builder Ubuntu-AArch32-native-extended-gdbserver-m32, " gdb-buildbot
2018-04-17  1:01 ` Breakage on builder Ubuntu-AArch32-native-gdbserver-m32, " gdb-buildbot
2018-04-17  1:06 ` Breakage on builder Ubuntu-AArch32-m32, " gdb-buildbot

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=20180416112251.GU3684@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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