public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: spyffe@mail.goo.ne.jp
Cc: gcc@gcc.gnu.org
Subject: Re: SUCCESS alpha-ev56 gcc-3.1
Date: Mon, 08 Jul 2002 11:27:00 -0000	[thread overview]
Message-ID: <20020708104817.C4726@us.ibm.com> (raw)
In-Reply-To: <20020630060744.54105.qmail@mail.goo.ne.jp>; from spyffe@mail.goo.ne.jp on Sun, Jun 30, 2002 at 03:07:44PM +0900

On Sun, Jun 30, 2002 at 03:07:44PM +0900, spyffe@mail.goo.ne.jp wrote:
> 
> I have succeeded building gcc-3.1 on the Alpha EV56.
> Detailed information is attached:
> 
> < Output of config.guess >--------------------------
> alphaev56-unknown-linux-gnu

Thanks!  Your message is linked from the GCC 3.1 build status list at
http://gcc.gnu.org/gcc-3.1/buildstat.html.

Janis

      reply	other threads:[~2002-07-08 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-30  7:51 spyffe
2002-07-08 11:27 ` Janis Johnson [this message]

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=20020708104817.C4726@us.ibm.com \
    --to=janis187@us.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=spyffe@mail.goo.ne.jp \
    /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).