From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>,
GDB Discussion <gdb@sources.redhat.com>
Subject: Re: ia64 target?
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <1010314052325.ZM17343@ocotillo.lan> (raw)
In-Reply-To: <3AAEA47E.339FF4BD@cygnus.com>
On Mar 13, 5:51pm, Andrew Cagney wrote:
> What is a good ia64 target? The maintainer file currently notes:
>
> ia64 (--target=ia64-elf broken)
>
> if I try to configure that, nothing interesting happens (the GDB
> directory didn't appear to even be created).
>
> Could someone suggest a better generic ia64 target that can be used to
> build a cross debug ia64 GDB.
How about...
--target=ia64-unknown-linux
I've successfully done a configure and make with
--target=ia64-unknown-linux on the following hosts:
i386-unknown-freebsd4.2
i386-unknown-netbsdelf1.5
i386-pc-solaris2.8
i686-pc-linux-gnu
ia64-unknown-linux
Of course, this only takes care of the build portion. If you want to
(somehow) test the resulting gdb, you need to have access to an IA-64
machine running Linux or a simulator (running Linux).
See http://www.software.hp.com/products/LIA64/overview4a.htm for info
on an IA-64 simulator. (I did much of the initial development with an
i686-pc-linux-gnu cross ia64-unknown-linux GDB using HP's ski
simulator. It is able to boot Linux and runs amazingly well.)
It may also be possible to use HP's NUE environment to do the testing
I have not tried this.
Kevin
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner [this message]
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` J.T. Conklin
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=1010314052325.ZM17343@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).