From: Mumit Khan <khan@xraylith.wisc.EDU>
To: binutils@sourceware.cygnus.com
Subject: Re: binutils newer than 2.9.1
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <199906090254.VAA06532@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <375C6095.4CCAA4D7@dgs.monash.edu.au>
On Tue, 8 Jun 1999, Brendan Simon wrote:
> Mumit Khan wrote:
>
> > To get what I call binutils-2.9.4 in my howto, you can get either get
> > the whole Cygwin source tree [1] (big!), or just get the pieces that
> > form binutils separately [2] that you can combine to re-create the 2.9.4
> > tree.
[...]
>
> I assume these files have other updates for targets other than
> cygwin32/mingw32. Is that correct ?
> Is this site likely to be maintained/updated regularly or do you think that I
> am better off using CVS and checking out snapshots that are known to be
> reasonably reliable ?
I'm in no position to judge whether the binutils packaged with Cygwin
works well with targets other than pe-coff or not. I only use this for
the various x86-win32 targets that I use, and use binutils-2.9.1 + patches
that are on the net for other targets (including ppc-eabi).
I do remember that I had some trouble with ppc-eabi when using binutils
2.9.4 (forward labels didn't have the right offset or some such thing),
and ended up using 2.9.1.
If you're supporting many targets, getting it out of CVS is probably the
way to go (don't forget to run the testsuite!).
Regards,
Mumit
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Brendan Simon
1999-07-01 0:00 ` Mumit Khan
1999-07-01 0:00 ` Brendan Simon
1999-07-01 0:00 ` Mumit Khan [this message]
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Brendan Simon
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Charles Gauthier
1999-07-01 0:00 ` Ian Lance Taylor
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=199906090254.VAA06532@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=binutils@sourceware.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).