This is the mail archive of the
mailing list for the GCC project.
suggestions for messages about successful builds
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: gcc at gcc dot gnu dot org
- Date: Wed, 27 Feb 2002 10:29:59 -0800
- Subject: suggestions for messages about successful builds
As the person who updates the GCC 3.0 build status list I've got some
requests, some of which have been brought up by others recently.
First of all, please look at the list in the "Final Installation"
section of the installation instructions for information to include in
a message about a successful build. Remember that your message will be
linked from the build status list and that other people who are planning
to build for the same platform are likely to look at your message, so
include any information that might be useful to those people.
If you didn't do a bootstrap, or if there were any errors in the build
or install, then it was not successful, so please don't report it as a
Ideally, the build status list should not just be for successful builds,
but for successful builds of usable compilers and libraries. Running
the testsuite is not difficult, although if you haven't done it before
you'll probably need to build and install dejagnu, tcl, and expect.
Once you've done that, they'll be available to let you test future
releases. The test results are likely to include unexpected failures.
Some of these you don't need to worry about, but others you do. I don't
know of a good way to tell the difference (apart from investigating each
failure) except to compare your failures to those on a similar platform.
You can make that easier for others by using contrib/test_summary to
submit your test results and include a link to that message in your
"successful build" message.
Active GCC developers can help by submitting messages about successful
builds on platforms they use regularly, with links to their test