From: Andrew Cagney <ac131313@ges.redhat.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: gdb@sources.redhat.com, Peter.Barada@Motorola.com
Subject: Re: Can't build m68k-linux gdb-5.2.1
Date: Mon, 19 Aug 2002 18:34:00 -0000 [thread overview]
Message-ID: <3D619C86.3080500@ges.redhat.com> (raw)
In-Reply-To: <200208192254.g7JMsMe09414@hyper.wm.sps.mot.com>
> I'm trying to build a gdb for m68k-linux, configured as:
> All the missing references are in gdb/m68klinux-nat.c, so I'd assume
> this is supposed to be built, but isn't for --target=m68k-linux. Does
> anyone have any idea how I can get it to be built?
Looks like for the moment you'll need to use m68k-elf.
The file m68klinux-nat.c should only contain stuff for a native build
(eg ptrace interface). The OS dependant, but not specific to native, is
typically put in a file like m68k-linux-tdep.c. cf m68knbsd-tdep.c.
Patches against mainline welcome (do you have an FSF assignment?).
It should also be noted that GDB's mainline m68k was recently
multi-arched so while the m68k-elf should be ok, I'm not sure what the
state of m68k-linux-gnu is.
Would you be able to create abug report to track this:
http://sources.redhat.com/gdb/bugs/
> While I'm at it, how do I configure(and build) a gdbserver to run on
> m68k-linux that's built on an x86-linux machine?
>
> All help is appreciated.
You'll need to config/compile it using a cross compiler
(m68k-linux-gnu-gcc say).
enjoy,
Andrew
next prev parent reply other threads:[~2002-08-20 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 15:54 Peter Barada
2002-08-19 18:34 ` Andrew Cagney [this message]
2002-08-20 6:33 ` Peter Barada
2002-08-20 6:48 ` Andrew Cagney
2002-08-20 7:03 ` Daniel Jacobowitz
2002-08-20 7:56 ` Andrew Cagney
2002-08-20 7:51 ` Peter Barada
2002-08-19 18:53 ` Daniel Jacobowitz
2002-08-20 6:40 ` Peter Barada
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=3D619C86.3080500@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=Peter.Barada@Motorola.com \
--cc=gdb@sources.redhat.com \
--cc=pbarada@mail.wm.sps.mot.com \
/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