From: Daniel Jacobowitz <dan@debian.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alex Gonzalez <langabe@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Jump/branch to external symbol
Date: Fri, 6 Jan 2006 09:52:16 -0500 [thread overview]
Message-ID: <20060106145216.GA6849@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0601061147540.25759@blysk.ds.pg.gda.pl>
On Fri, Jan 06, 2006 at 11:51:56AM +0000, Maciej W. Rozycki wrote:
> On Fri, 6 Jan 2006, Alex Gonzalez wrote:
>
> > I am happy with the patch for binutils-2.15, and I would need a
> > solution for binutils-2.13.
> >
> > Can anybody offer any help?
>
> Well, the most obvious solution is upgrading to the current release,
> which is 2.16.1 now. Otherwise you are probably on your own -- 2.15 is
> already somewhat old and 2.13 is ancient.
Or better yet to trunk and you won't need any patches for this.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-06 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 10:41 Jump/branch to external symbol Alex Gonzalez
2006-01-06 11:51 ` Maciej W. Rozycki
2006-01-06 14:52 ` Daniel Jacobowitz [this message]
2006-01-06 17:50 ` Alex Gonzalez
2006-01-07 11:15 ` Ralf Baechle
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=20060106145216.GA6849@nevyn.them.org \
--to=dan@debian.org \
--cc=langabe@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox