Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: ac131313@ges.redhat.com
Cc: Peter.Barada@Motorola.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:51:00 -0000	[thread overview]
Message-ID: <200208201451.g7KEpNx17372@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <3D62489D.5020502@ges.redhat.com> (message from Andrew Cagney on Tue, 20 Aug 2002 09:48:13 -0400)


>> 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.

After thinking about it a bit more, you are correct.  gdb must be able
to be built on a host targeted for m68k-linux since I'd expect to run
m68k-linux-gdb on my x86 box, using a gdbserver running on the target.

>>Would you be able to create abug report to track this:
>>http://sources.redhat.com/gdb/bugs/

I've reported that gdb-5.2.1 can't build --traget=m68k-linux on my
i686-linux-gnu box dup to missing m68k_linux_in_sigtramp symbol.

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)


  parent reply	other threads:[~2002-08-20 14:51 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
2002-08-20  7:56         ` Andrew Cagney
2002-08-20  7:51       ` Peter Barada [this message]
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=200208201451.g7KEpNx17372@hyper.wm.sps.mot.com \
    --to=pbarada@mail.wm.sps.mot.com \
    --cc=Peter.Barada@Motorola.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@sources.redhat.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