public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Ian Lance Taylor <ian@airs.com>
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: <375C6236.D0348849@dgs.monash.edu.au> (raw)
In-Reply-To: <19990607140936.1597.qmail@daffy.airs.com>

Ian Lance Taylor wrote:

>    Date: Mon, 07 Jun 1999 06:04:18 +0000
>    From: Brendan Simon <brendan@dgs.monash.edu.au>
>
>    Where can I find binutils releases that are newer version 2.9.1 ?
>
> There are no official binutils releases newer than 2.9.1.  The CVS
> binutils sources happen to report themselves as 2.9.4 currently, but
> that is strictly an internal number.  There is no single 2.9.4
> release.
>
>    I read in one of Mumit Khan's cross-compiler howtos that 2.9.4 is
>    recommended for building the cygwin32/mingw32 compilers.
>
> The cygwin releases include binutils snapshots which have been tested
> for cygwin.  Probably the latest cygwin release included a binutils
> snapshot marked 2.9.4 (it's been 2.9.4 for a while).  But, again,
> there is no single 2.9.4 release.
>
>    The official binutils site (sourceware.cygnus.com as far as I am aware)
>    has 2.9.1as the latest release.  This has been around for quite awhile
>    and I'm sure there must have been further releases.  Has the site been
>    kept up to date ?
>
> The site is more or less up to date.
>
> I'm afraid we are very far behind in actually making an official
> release.  I still have a stack of patches and bug reports I need to
> get through, although I have been making a little progress recently.
>
> Ian

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-???

Brendan Simon.

  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 [this message]
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=375C6236.D0348849@dgs.monash.edu.au \
    --to=brendan@dgs.monash.edu.au \
    --cc=binutils@sourceware.cygnus.com \
    --cc=ian@airs.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).