From: jtc@redback.com (J.T. Conklin)
To: Kevin Buettner <kevinb@cygnus.com>
Cc: 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: <5mzoelny3t.fsf@jtc.redback.com> (raw)
In-Reply-To: <1010314052325.ZM17343@ocotillo.lan>
>>>>> "Kevin" == Kevin Buettner <kevinb@cygnus.com> writes:
>> 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.
Kevin> How about...
Kevin>
Kevin> --target=ia64-unknown-linux
Kevin>
Kevin> I've successfully done a configure and make with
Kevin> --target=ia64-unknown-linux on the following hosts:
Kevin>
Kevin> i386-unknown-freebsd4.2
Kevin> i386-unknown-netbsdelf1.5
Kevin> i386-pc-solaris2.8
Kevin> i686-pc-linux-gnu
Kevin> ia64-unknown-linux
Note that all of these hosts use ELF/svr4 shared libraries. On
others, it fails to build. I believe all of the Linux targets suffer
from this bug.
That might be considered an OK limitation for Linux targets. But if
we're going to have a config listed in the MAINTAINERS list so we can
use it to verify that global changes don't break builds, we have to
ensure that those configs build on all hosts.
--jtc
--
J.T. Conklin
RedBack Networks
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
2001-03-21 15:59 ` J.T. Conklin [this message]
2001-03-21 15:59 ` Kevin Buettner
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 ` Andrew Cagney
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=5mzoelny3t.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.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).