From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Mumit Khan <khan@xraylith.wisc.edu>
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: <375C6095.4CCAA4D7@dgs.monash.edu.au> (raw)
In-Reply-To: <199906071604.LAA02771@mercury.xraylith.wisc.edu>
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.
>
> [1] ftp://sourceware.cygnus.com/pub/cygwin/cygwin-b20/
> [2] ftp://sourceware.cygnus.com/pub/cygwin/cygwin-b20/src-by-top-dir/
>
> Here's what I had posted to the Cygwin mailing list a while back:
>
> Date: Thu, 18 Feb 1999 14:40:35 CST
> cc: cygwin mailing list <cygwin@sourceware.cygnus.com>
> Subject: Re: How to compile binutils
>
> Thanks to DJ's addition of toplevel.tar.bz2, it's very complete.
> Here's a list of files needed for binutils-2.9.4 (I just wrote this
> up yesterday for my mingw-cross-howto guide, so you're in luck):
>
> bfd.tar.bz2 gas.tar.bz2 ld.tar.bz2 toplevel.tar.bz2
> binutils.tar.bz2 gprof.tar.bz2 libiberty.tar.bz2
> config.tar.bz2 include.tar.bz2 opcodes.tar.bz2
> etc.tar.bz2 intl.tar.bz2 texinfo.tar.bz2
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 ?
Thanks,
Brendan Simon.
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 [this message]
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
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=375C6095.4CCAA4D7@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=binutils@sourceware.cygnus.com \
--cc=khan@xraylith.wisc.edu \
/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).