public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "J.F. Noonan" <jfn@msc.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3432: Attempt to build on DEC UNIX 5.0 dies with internal compiler error
Date: Sun, 24 Feb 2002 17:26:00 -0000 [thread overview]
Message-ID: <20020225011603.17253.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/3432; it has been noted by GNATS.
From: "J.F. Noonan" <jfn@msc.com>
To: <rodrigc@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<jfn@msc.com>, <nobody@gcc.gnu.org>, <rodrigc@gcc.gnu.org>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: bootstrap/3432: Attempt to build on DEC UNIX 5.0 dies with
internal compiler error
Date: Sun, 24 Feb 2002 19:14:36 -0600 (CST)
I don't know. I've just built and installed 3.0.3 on some red hat
7.1 boxes (on which 3.0 had installed OK), but I haven't tried it
on dec unix yet. I will try this week and report back.
--
Joseph F. Noonan
Rigaku/MSC Inc.
jfn@msc.com cel:281-433-2731
voice:281-363-1033 x117 fax:281-364-3644
On 24 Feb 2002 at 3:10am rodrigc@gcc.gnu.org wrote:
> Synopsis: Attempt to build on DEC UNIX 5.0 dies with internal compiler error
>
> State-Changed-From-To: open->feedback
> State-Changed-By: rodrigc
> State-Changed-When: Sat Feb 23 19:10:02 2002
> State-Changed-Why:
> Is this still a problem? We have successful build reports
> on Tru64Unix here:
> http://gcc.gnu.org/gcc-3.0/buildstat.html
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3432
>
next reply other threads:[~2002-02-25 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 17:26 J.F. Noonan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 13:26 rodrigc
2002-02-23 19:16 rodrigc
2001-06-26 13:06 jfn
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=20020225011603.17253.qmail@sources.redhat.com \
--to=jfn@msc.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).