From: Janis Johnson <janis187@us.ibm.com>
To: gcc@gcc.gnu.org
Subject: additions to GCC 3.2 build status list
Date: Sat, 23 Nov 2002 01:14:00 -0000 [thread overview]
Message-ID: <20021122164146.A2667@us.ibm.com> (raw)
Several messages about successful builds for GCC 3.2.1 are now linked from
the GCC 3.2 build status list at http://gcc.gnu.org/gcc-3.2/buildstat.html.
In the past I've sent an individual reply for each build message, but with
the volume of such messages becoming greater with each release I'd like to
know if my responses are worthwhile. If people like them I'll keep doing
them; otherwise I'll add the links and then occasionally send messages
like this with a list of what new entries have been added, possibly copied
to the people who posted the build reports.
Here's what was just added to gcc-3.2/buildstat.html, with the log entry:
Add entries for 3.2.1:
hppa2.0w-hp-hpux11.00
i686-pc-cygwin (Athlon) (Cygwin 1.3.14, Windows 98SE)
i686-pc-linux-gnu (Red Hat 7.2, glibc 2.2.4, binutils 2.13.1, kernel 2.4.7)
i686-pc-linux-gnu (SuSE 5.0, glibc 2.2.5, kernel 2.4.19)
i686-pc-linux-gnu (SuSE 7.1, glibc 2.2-17, binutils 2.13, kernel 2.4.5)
powerpc-apple-darwin6.1 (Darwin 6.2)
powerpc-unknown-linux-gnu (SuSE 7.1, glibc 2.2, binutils 2.13, kernel 2.4.2)
sparc-sun-solaris2.7
Janis Johnson
IBM Linux Technology Center
next reply other threads:[~2002-11-23 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 1:14 Janis Johnson [this message]
2002-11-23 1:27 ` kwall
2002-11-23 4:17 ` Kaveh R. Ghazi
2002-11-23 8:49 ` Gerald Pfeifer
2003-02-25 21:49 Janis Johnson
2003-02-26 3:39 ` Gabriel Dos Reis
2003-05-09 23:12 Janis Johnson
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=20021122164146.A2667@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@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).