public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gcc k6 testing account <caligula@cam029208.student.utwente.nl>
To: <gcc@gcc.gnu.org>
Subject: Build status page:Succes and failures.
Date: Fri, 07 Dec 2001 07:52:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0112071542330.6221-100000@cam029208.student.utwente.nl> (raw)


Ave gcc people.

I'm following the build status page discussion and here are my 2 cents.

When 3.0.2 was released I reported a succesfull build on 
k6-redhat-linux-gnu and submitted the testresults with 
test_summary.(October 24). Following this discussion,I tried to build 3.0 
and 3.0.1. Those bootstraps were NOT succesfull.

So here's the summary on the k6 side.

gcc-3.0    -->No bootstrap.
gcc-3.0.1  -->No bootstrap.
gcc-3.0.2  -->Succsesfull bootstrap.

gcc-3.0.x-cvs  -->Succesfull bootstrap.
gcc-3.1-cvs    -->Succesfull bootstrap.

All this with:
gcc      :     2.96-97
binutils :     2.11.90.0.8
glibc    :     2.2.4

So maybe there could be a warning note on the build status page that 
k6-redhat-linux-gnu bootstraps succesfully from 3.0.2 on. Just like 
s390-linux-gnu starts to bootstrap from 3.0.1 on.

Greetinx
Martijn Uffing
(please only reply to the list. This is a send only email-account)









             reply	other threads:[~2001-12-07 15:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07  7:52 Gcc k6 testing account [this message]
2001-12-07  9:40 ` Joe Buck
2001-12-12 10:35   ` Janis Johnson
2001-12-13 12:29     ` Gerald Pfeifer
2001-12-13 13:15       ` Janis Johnson
2001-12-13 16:54       ` Joe Buck
2001-12-13 17:38         ` Janis Johnson
2001-12-15 10:43     ` John Marshall
2001-12-17  9:08       ` Janis Johnson
2001-12-12 11:59   ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
2001-12-12 12:20     ` David Edelsohn
2001-12-12 14:48     ` David Edelsohn
2001-12-12 15:51       ` Joe Buck

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.LNX.4.33.0112071542330.6221-100000@cam029208.student.utwente.nl \
    --to=caligula@cam029208.student.utwente.nl \
    --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).