From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Andreas Schwab <schwab@suse.de>, gdb-patches@sources.redhat.com
Subject: Re: [Committed] More fixes for m68k-linux
Date: Fri, 13 Dec 2002 06:40:00 -0000 [thread overview]
Message-ID: <5.0.2.1.2.20021213112710.0331ea20@ics.u-strasbg.fr> (raw)
In-Reply-To: <200211231946.gANJk63p003036@whitebox.local>
All these patches were not
inserted in 5.3 branch thus
m68k native linux compilation of
GDB fails :(
Can we at least insert it now in the 5.3 branch?
So that if we release a 5.3.1 m68k linux compilation will be fixed.
At 20:46 23/11/2002, Andreas Schwab wrote:
>This patch fixes building m68k-linux natively. The inclusion of
>m68k-tdep.h in config/m68k/tm-linux.h is only temporary until the
>macros are turned into functions.
>
>Andreas.
>
>2002-11-23 Andreas Schwab <schwab@suse.de>
>
> * Makefile.in (m68k_tdep_h): Define.
> (abug-rom.o, cpu32bug-rom.o, dbug-rom.o, m68k-tdep.o, m68klinux-nat.o)
> (remote-est.o, rom68k-rom.o): Add $(m68k_tdep_h).
> * m68k-tdep.c: Move register number enum ...
> * m68k-tdep.h: ... to this new file and rename the constants from
> E_* to M68K_*. All uses changed.
> * config/m68k/tm-m68k.h (D0_REGNUM, A0_REGNUM): Remove definitions.
> * abug-rom.c: Include "m68k-tdep.h". Use
> M68K_D0_REGNUM/M68K_A0_REGNUM instead of D0_REGNUM/A0_REGNUM.
> * cpu32bug-rom.c: Likewise.
> * dbug-rom.c: Likewise.
> * m68k-tdep.c: Likewise.
> * m68klinux-nat.c: Likewise.
> * remote-est.c: Likewise.
> * rom68k-rom.c: Likewise.
> * config/m68k/tm-linux.h: Likewise.
prev parent reply other threads:[~2002-12-13 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 11:46 Andreas Schwab
2002-12-13 6:40 ` Pierre Muller [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=5.0.2.1.2.20021213112710.0331ea20@ics.u-strasbg.fr \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
/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