From: Ian Lance Taylor <ian@airs.com>
To: brendan@dgs.monash.edu.au
Cc: 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: <19990609042043.1682.qmail@daffy.airs.com> (raw)
In-Reply-To: <375C6236.D0348849@dgs.monash.edu.au>
Date: Tue, 08 Jun 1999 00:22:14 +0000
From: Brendan Simon <brendan@dgs.monash.edu.au>
If I want later versions of binutils (I am unsure of how necessary this is)
then it would appear that CVS would be the best option and to checkout
snapshots that are known to be reasonably reliable. Would you suggest this
as a wise thing or to just stick with the stock standard 2.9.1 ? Maybe the
cygwin sources of binutils might be the best option ? My main targets of
interest are powerpc-eabi, powerpc-linux and m68k-???
I don't have a good answer to this question. binutils 2.9.1 is
certainly better tested than the CVS snapshots. For GNU/Linux, H.J.'s
snapshot releases are well tested. For anything else, I guess you
just have to balance newer sources with lack of testing. I don't know
how to resolve that balance for you.
If you have specific bugs that you want fixed, consider looking
through the CVS sources and picking out the bug fixes. If you can't
do that, using the CVS sources may be too risky for you, since you may
run into bugs you can't fix.
Ian
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
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Brendan Simon
1999-07-01 0:00 ` Ian Lance Taylor [this message]
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=19990609042043.1682.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=brendan@dgs.monash.edu.au \
/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).