From: Julian Back <jback@mpc-data.co.uk>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Building GDB 6.1 for SH target
Date: Wed, 26 May 2004 16:56:00 -0000 [thread overview]
Message-ID: <40B4CC04.7030600@mpc-data.co.uk> (raw)
In-Reply-To: <20040526124823.GA6310@nevyn.them.org>
Daniel Jacobowitz wrote:
>On Wed, May 26, 2004 at 12:30:29PM +0100, Julian Back wrote:
>
>
>>with a target of "sh-elf". I would be interested to know of any
>>specific changes I could make to reinstate the sh-linux port.
>>
>>
>
>Take a look at the osabi sniffers used by some other targets; SH needs
>to register one, and that will fix the warning. I don't know if it
>needs to do anything.
>
>If you're interested in working on the SH port, will you be able to
>file a copyright assignment?
>
>
Yes, that shouldn't be a problem. I can't guarantee to achieve anything
useful though!
Julian
prev parent reply other threads:[~2004-05-26 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 15:41 Julian Back
2004-05-26 1:31 ` Daniel Jacobowitz
2004-05-26 11:30 ` Julian Back
2004-05-26 11:57 ` shared library memory leak MuthuKumar-15
2004-05-26 12:48 ` Building GDB 6.1 for SH target Daniel Jacobowitz
2004-05-26 16:56 ` Julian Back [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=40B4CC04.7030600@mpc-data.co.uk \
--to=jback@mpc-data.co.uk \
--cc=drow@false.org \
--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