public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Janis Johnson <janis187@us.ibm.com>
Cc: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>,
	<gcc@gcc.gnu.org>, Paolo Carlini <pcarlini@unitus.it>
Subject: Re: Testing 3.1 g++ applications on cygwin
Date: Fri, 26 Apr 2002 08:36:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.44.0204261725030.71509-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20020426081919.A1552@us.ibm.com>

On Fri, 26 Apr 2002, Janis Johnson wrote:
> If you run into more things in the build and test guides that need
> updates, please point them out (or supply patches!).

Seconded.

> Somewhere out there is a tarball for POOMA with changes to make it
> easier to use for GCC testing, and somewhere else is a Perl script to
> build and test it.  It sure would be nice if they were linked from the
> POOMA build and test guide.

ftp://gcc.gnu.org/pub/gcc/infrastructure/pooma-gcc.tar.gz is linked
from http://gcc.gnu.org/gcc-3.1/criteria.html.

Paolo Carlini <pcarlini@unitus.it> also provided an update for
the testing-pooma.html page there.

Are we still missing something?

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

  reply	other threads:[~2002-04-26 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 23:26 Billinghurst, David (CRTS)
2002-04-26  8:20 ` Janis Johnson
2002-04-26  8:36   ` Gerald Pfeifer [this message]
2002-04-26  9:30     ` Janis Johnson
2002-04-26  9:47       ` Janis Johnson
2002-04-26 10:37 Peter Schmid
2002-04-26 14:16 ` Janis Johnson
2002-04-26 14:33   ` Gerald Pfeifer
2002-04-26 15:48     ` Janis Johnson
2002-04-26 16:09       ` Paolo Carlini
2002-04-27 11:45         ` Gerald Pfeifer

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=Pine.BSF.4.44.0204261725030.71509-100000@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=David.Billinghurst@riotinto.com \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=pcarlini@unitus.it \
    /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).