public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/931: VMS support looks bitrotten
Date: Tue, 02 Apr 2002 03:26:00 -0000 [thread overview]
Message-ID: <20020402112602.609.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/931; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <neil@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: other/931: VMS support looks bitrotten
Date: Tue, 2 Apr 2002 12:17:22 +0100 (BST)
On 2 Apr 2002 neil@gcc.gnu.org wrote:
> I believe VMS support is OK for 3.1 now? Douglas Rupp did a lot
> of work on this recently.
Alpha/OpenVMS support may be OK - it's for him to comment in this PR if
so. Maybe the PR should be assigned to him.
The file gcc.hlp is still present, and may be bitrotten. The docs in
install-old.texi and vms.texi are definitely out of date and need a
thorough overhaul. The current install manual install.texi needs to say
something about installing on VMS.
A decision is needed about whether VAX VMS is in principle supported
(albeit maybe bitrotten) or is desupported. This should probably depend
on whether it can use the Unix build procedure - if no version of VAX VMS
can use the Unix build procedure, VAX VMS should probably be desupported.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2002-04-02 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 3:26 Joseph S. Myers [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-12-27 22:16 Nathanael Nerode
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=20020402112602.609.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--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).