public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/931: VMS support looks bitrotten
Date: Fri, 27 Dec 2002 22:16:00 -0000 [thread overview]
Message-ID: <20021228061601.18046.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/931; it has been noted by GNATS.
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: other/931: VMS support looks bitrotten
Date: Sat, 28 Dec 2002 01:10:26 -0500
VAX/VMS support in GCC has officially been dropped and its files removed.
Alpha/OpenVMS support is OK and uses the Unix build procedure.
What's left are the following:
gcc.hlp: Should this be updated? Deleted? What?
vms.texi: This is more up to date than it used to be, but an Alpha/OpenVMS
maintainer still needs to go through it to make it accurate.
install-old.texi: Still-relevant parts of this (if there are any) need to be
migrated into install.texi.
This shouldn't be too hard overall, but it can only be done by an OpenVMS
person, 'cause they're the only ones who know what to do. Perhaps it could
be assigned to some such person? :-)
--Nathanael
next reply other threads:[~2002-12-28 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 22:16 Nathanael Nerode [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 23:16 Joseph S. Myers
2003-01-11 22:44 neroden
2002-12-28 4:26 Joseph S. Myers
2002-04-02 3:26 Joseph S. Myers
2002-04-02 1:22 neil
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=20021228061601.18046.qmail@sources.redhat.com \
--to=neroden@twcny.rr.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).