From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Peter Barada <pbarada@mail.wm.sps.mot.com>,
Peter.Barada@Motorola.com, gdb@sources.redhat.com
Subject: Re: Can't build m68k-linux gdb-5.2.1
Date: Tue, 20 Aug 2002 07:03:00 -0000 [thread overview]
Message-ID: <20020820140403.GA28061@nevyn.them.org> (raw)
In-Reply-To: <3D62489D.5020502@ges.redhat.com>
On Tue, Aug 20, 2002 at 09:48:13AM -0400, Andrew Cagney wrote:
> >>>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?).
> >
> >
> >1) I can use m68k-elf for now.
> >2) I'm still working the legal department to come up with an
> > assignment to cover changes for gdb.
> >
> >
> >>Would you be able to create abug report to track this:
> >>http://sources.redhat.com/gdb/bugs/
> >
> >
> >Shold the bug be that m68k-linux should not build on a machine that is
> >*not* m68k-linux, or that it should build for m68k-linux only if
> >CC is a cross-compiler?
>
> A m68k-linux-gnu targeted GDB should build on any UNIX like host.
>
> >>>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).
> >
> >
> >Do you have a configure command line to suggest?
>
> I think DanielJ covered this (However, we desperatly need doco
> explaining the procedure :-/).
It's already there. In gdbserver/README. I have a promise to Eli
sitting in my inbox to add it to gdb/INSTALL, except that I just
noticed there _isn't_ a gdb/INSTALL. So I don't know how much more
prominent I can make it.
No one reads the READMEs...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-20 14:03 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
2002-08-20 6:33 ` Peter Barada
2002-08-20 6:48 ` Andrew Cagney
2002-08-20 7:03 ` Daniel Jacobowitz [this message]
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=20020820140403.GA28061@nevyn.them.org \
--to=drow@mvista.com \
--cc=Peter.Barada@Motorola.com \
--cc=ac131313@ges.redhat.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