From: mike stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, steve@moshier.net
Subject: Re: What is a successful build?
Date: Mon, 25 Feb 2002 13:01:00 -0000 [thread overview]
Message-ID: <200202251955.LAA11873@kankakee.wrs.com> (raw)
Imagine a world where we run make check just after build and before
install, and if the line '# of unexpected failures' comes out in any
.log file, we don't install and fail the build. :-)
Ok, I'll go away now...
> Date: Sun, 24 Feb 2002 16:28:40 -0500 (EST)
> From: Stephen L Moshier <steve@moshier.net>
> To: gcc@gcc.gnu.org
> According to
> http://gcc.gnu.org/gcc-3.0/buildstat.html
> gcc-3.0.4 builds successfully on various computers, but the
> regression test results are not discussed very much.
next reply other threads:[~2002-02-25 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 13:01 mike stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-24 13:39 Stephen L Moshier
2002-02-24 13:44 ` Christian Jönsson
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=200202251955.LAA11873@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=gcc@gcc.gnu.org \
--cc=steve@moshier.net \
/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).