From: Joel Sherrill <joel@OARcorp.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: binutils 2.8.1 problem compiling gcc-2.8.0-971206
Date: Mon, 08 Dec 1997 11:32:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971208133005.16589C-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199712081920.OAA04767@subrogation.cygnus.com>
On Mon, 8 Dec 1997, Ian Lance Taylor wrote:
> Date: Mon, 8 Dec 1997 13:08:19 -0600 (CST)
> From: Joel Sherrill <joel@OARcorp.com>
>
> I have been wondering whether the egcs and gcc 2.8 releases imply binutils
> and newlib should have releases as well. I know the as.new -> as-new
> change is something which must be in sync for the one-tree build procedure
> to work.
>
> Certainly there should be a binutils release. Unfortunately, it's a
> question of available time to produce one. I'll try to start the
> process soon.
I understand completely. It is tough to get things to stabilize, find
time to test, and hope that the releases of multiple interdependent
packages happen close to one another.
I am trying to get an RTEMS release out the door now. And gcc 2.8/egcs
1.0 are the first gcc releases with RTEMS support.
--joel
next prev parent reply other threads:[~1997-12-08 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-08 6:09 Joel Sherrill
1997-12-08 9:26 ` Ian Lance Taylor
1997-12-08 11:20 ` Joel Sherrill
1997-12-08 11:20 ` Ian Lance Taylor
1997-12-08 11:32 ` Joel Sherrill [this message]
1997-12-08 14:38 ` H.J. Lu
1997-12-08 14:14 ` Ian Lance Taylor
1997-12-08 14:22 ` H.J. Lu
1997-12-08 14:38 ` Ian Lance Taylor
1997-12-11 8:35 ` soname patch for gas2 H.J. Lu
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=Pine.BSF.3.96.971208133005.16589C-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
--cc=ian@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).