From: Andrew Cagney <ac131313@redhat.com>
To: Matthew Wilcox <willy@debian.org>
Cc: law@redhat.com, Alan Modra <amodra@bigpond.net.au>,
binutils@sources.redhat.com, parisc-linux@parisc-linux.org
Subject: [parisc-linux] Re: [PATCH] space register 0 changes for hppa
Date: Mon, 24 Feb 2003 16:49:35 -0500 [thread overview]
Message-ID: <3E5A936F.6070401@redhat.com> (raw)
In-Reply-To: 20030224184225.N2938@parcelfarce.linux.theplanet.co.uk
> On Mon, Feb 24, 2003 at 11:39:52AM -0700, law@redhat.com wrote:
>
>> Err, I built it without difficulty a few months ago (I don't do nearly as
>> much PA work as I used to). Presumably you have an HPUX box, right? That's
>> the easiest way to get it build and running.
>
>
> nope, no hpux, only i386-linux and hppa-linux around here. trying to
> get binutils cvs to build a cross i386->hppa gdb dies in tix (no tk8.4
> directory), trying with just `make all-binutils all-gdb' dies being
> unable to find dl.h or machine/save_state.h.
Unfortunatly, no one got the i386->hppa GDB to build so asking you to do
that isn't reasonable. If you've a hppa-linux-gnu box, can you just try
binutils, `objdump --disassemble`?
Andrew
> so switch to trying native on an hppa-linux host with gdb-5.3. that dies
> claiming hppa-linux is unsupported. apply the debian patches. that build
> dies trying to find texc.pro.
>
> i'm willing to put in a certain amount of time & effort, but this is
> too much.
>
> -- "It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-02-24 21:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 18:58 [parisc-linux] [PATCH] space register 0 changes for hppa Matthew Wilcox
2003-02-24 6:24 ` [parisc-linux] " Alan Modra
2003-02-24 12:48 ` Matthew Wilcox
2003-02-24 12:48 ` Matthew Wilcox
2003-02-24 15:01 ` law
2003-02-24 15:01 ` law
2003-02-24 14:59 ` Matthew Wilcox
2003-02-24 16:16 ` law
2003-02-24 16:16 ` law
2003-02-24 14:59 ` Matthew Wilcox
2003-02-24 18:23 ` Matthew Wilcox
2003-02-24 18:39 ` law
2003-02-24 18:39 ` law
2003-02-24 18:42 ` Matthew Wilcox
2003-02-24 18:47 ` Daniel Jacobowitz
2003-02-24 18:47 ` Daniel Jacobowitz
2003-02-24 21:49 ` Andrew Cagney [this message]
2003-02-24 21:57 ` Matthew Wilcox
2003-02-24 22:11 ` Andrew Cagney
2003-02-24 22:11 ` Andrew Cagney
2003-02-24 22:19 ` Matthew Wilcox
2003-02-25 0:21 ` Alan Modra
2003-02-25 0:21 ` Alan Modra
2003-02-24 22:19 ` Matthew Wilcox
2003-02-24 21:57 ` Matthew Wilcox
2003-02-24 21:49 ` Andrew Cagney
2003-02-24 18:42 ` Matthew Wilcox
2003-02-24 18:23 ` Matthew Wilcox
2003-02-24 6:24 ` Alan Modra
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=3E5A936F.6070401@redhat.com \
--to=ac131313@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=law@redhat.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.