From: Jeffrey A Law <law@cygnus.com>
To: joel@OARcorp.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: include/elf/hppa.h in gdb 4.18
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <15249.929995792@upchuck.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9906211444540.30178-100000@oar3remote>
In message < Pine.LNX.4.10.9906211444540.30178-100000@oar3remote >you write:
> > Don't even try to use the PA ELF tools right now. They're under major
> > reorganization.
>
> OK. I was just trying to update the gdb RTEMS patch to 4.18.
If you're just trying to get up to gdb-4.18 you can probably make a little
tweak or two. For some reason I thought you were trying to get the
mainline code building. You can probably delete the offending code in your
gdb-4.18 rtems patch.
> > I'd forgotten RTEMS depended on this stuff. Ugh.
>
> The RTEMS target is not much more than an alias. If I need to change to
> basing it on another target, it is not a big deal. Just let me know what
> the best embedded hppa1.1 target is once this settles out again.
I doubt you'll need to change it. We're just going to have to create a lot of
construction debris in the PA ELF code for a while.
I'll be primarily concentrating on 64bit ELF, but it's going to have serious
impact on the 32bit ELF tools. The Linux folks are going to be beating on the
32bit ELF tools (hopefully in parallel).
jeff
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 joel
1999-07-01 0:00 ` joel
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` joel
1999-07-01 0:00 ` Jeffrey A Law [this message]
1999-07-01 0:00 ` joel
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=15249.929995792@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=joel@OARcorp.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).