From: Victor Danilchenko <danilche@cs.umass.edu>
To: help-gcc@gnu.org
Subject: When is GCC 2.95.3 due?
Date: Wed, 29 Dec 1999 09:46:00 -0000 [thread overview]
Message-ID: <386A4814.3FB04C6D@cs.umass.edu> (raw)
Can anyone give me a ballpark figure?.. A couple of weeks, a couple of
months? I need it only because I have to decide if I should build GCC
2.95.2 now for my department (on 8 different platforms -- so it's a
major undertaking), or If I should wait for a couple of weeks until
2.95.3 comes out. I do have to rebuild it because our g++-3 include path
is broken, so I figured that if I am going to recompile, I should
combine that with an upgrade.
Any insights would be much appreciated. This is not info that I would
try to use in any manner but a ballpark guide to a single decision.
which decision can be made either way anyway.
--
Victor Danilchenko
WARNING: multiple messages have this Message-ID
From: Victor Danilchenko <danilche@cs.umass.edu>
To: help-gcc@gnu.org
Subject: When is GCC 2.95.3 due?
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <386A4814.3FB04C6D@cs.umass.edu> (raw)
Message-ID: <19991231222400.UG81q7H4ffxcHrfJG5ip29jJYjBL6ipDCKQtu0hyAGY@z> (raw)
Can anyone give me a ballpark figure?.. A couple of weeks, a couple of
months? I need it only because I have to decide if I should build GCC
2.95.2 now for my department (on 8 different platforms -- so it's a
major undertaking), or If I should wait for a couple of weeks until
2.95.3 comes out. I do have to rebuild it because our g++-3 include path
is broken, so I figured that if I am going to recompile, I should
combine that with an upgrade.
Any insights would be much appreciated. This is not info that I would
try to use in any manner but a ballpark guide to a single decision.
which decision can be made either way anyway.
--
Victor Danilchenko
next reply other threads:[~1999-12-29 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-29 9:46 Victor Danilchenko [this message]
1999-12-29 10:02 ` Jeffrey A Law
1999-12-29 11:48 ` Victor Danilchenko
1999-12-31 22:24 ` Victor Danilchenko
1999-12-31 22:24 ` Jeffrey A Law
1999-12-31 22:24 ` Victor Danilchenko
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=386A4814.3FB04C6D@cs.umass.edu \
--to=danilche@cs.umass.edu \
--cc=help-gcc@gnu.org \
/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).