From: Andrew Cagney <ac131313@ges.redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/in] Add (broken) hppa-elf target
Date: Sun, 18 Aug 2002 11:30:00 -0000 [thread overview]
Message-ID: <3D5FE7C5.1000502@ges.redhat.com> (raw)
In-Reply-To: <200208181803.g7II32ag029618@elgar.kettenis.dyndns.org>
> Date: Sun, 18 Aug 2002 13:27:56 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
>
> PS: To give you a headache :-) Even though a native i386-ibm-aix won't
> build, there is a good chance that an i386-ibm-aix host will build an
> i386-ibm-aix cross debugger. This is correct behavour because a cross
> debugger should be buildable on any host :-)
>
> Yup. Except that --target=i386-ibm-aix won't give you exactly a
> i386-ibm-aix cross-debuger. It will give you the same generic i386
> cross-debuger as --target=i386-elf or --target=i386-whatever-junk.
> Suppose i386-ibm-aix had a rather peculiar ABI that's really
> incompatible with the generic i386 ABI. The resulting GDB would not
> be very useful. Shouldn't we somehow warn against this?
(I've ended up debugging an arm target using an x86 gdb so it is still
useful :-)
I guess we could. src/configure.in currently disables the ia64-elf
target because it doesn't build. A warning message is printed but it is
burried in amongst all the other autoconf output.
Anyway, I think it is easier in cases such as this, to just let GDB
built the best it can. If a warning is really needed then perhaps have
the OS sniffer detect and report something (Hmm, I just deleted the
messaging indicating that the OSABI was unknown :-( ).
enjoy,
Andrew
prev parent reply other threads:[~2002-08-18 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-18 9:14 Andrew Cagney
2002-08-18 9:48 ` Mark Kettenis
2002-08-18 10:28 ` Andrew Cagney
2002-08-18 11:03 ` Mark Kettenis
2002-08-18 11:22 ` Daniel Jacobowitz
2002-08-18 11:30 ` Andrew Cagney [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=3D5FE7C5.1000502@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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