This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: build status for cross builds?

This patch (sent to the main GCC mailing list to get more exposure) adds
a new page at the GCC web site for reports of successful GCC 3.0 cross
builds.  This is separate from the existing build status page so its
format can evolve as needed.  The entries are for reports of cross
builds that were received this month.

I volunteer to maintain this page (as I do the existing GCC 3.0 build
status page) unless someone else would really like to do it.

I tried to validate the new page with the W3C HTML validation service
using the extra html lines shown in contribute.html, but it complained
about the lack of specification of the character set; any ideas about
what I might have done wrong would be greatly appreciated.

There isn't a ChangeLog for htdocs, but if there were here's what the
entry would be for this patch:

2002-01-17  Janis Johnson  <janis187@us.ibm.com>

	* gcc-3.0/index.html: Add link to cross build status page.
	* gcc-3.0/buildstat-cross.html: New file.

Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/index.html,v
retrieving revision 1.6
diff -u -p -r1.6 index.html
--- index.html	2002/01/06 22:33:11	1.6
+++ index.html	2002/01/17 20:48:08
@@ -35,7 +35,8 @@ and many other new features, relative to
 href="features.html">new features</a> page for a more complete
 list.</p>
 
-<p>A list of <a href="buildstat.html">successful builds</a> is updated
+<p>Lists of <a href="buildstat.html">successful builds</a> and
+<a href="buildstat-cross.html">successful cross builds</a> are updated
 as new information becomes available.</p>
 
 <p>The GCC developers would like to thank the numerous people that
--- /dev/null	Tue May 23 09:27:54 2000
+++ buildstat-cross.html	Thu Jan 17 13:04:20 2002
@@ -0,0 +1,89 @@
+<html>
+
+<head>
+<title>Status of Cross Builds for GCC 3.0</title>
+</head>
+
+<body>
+<h1 align="center">Status of Cross Builds for GCC 3.0</h1>
+
+<p>This list summarizes reports of cross builds for GCC 3.0.x, with
+links to the archived mail messages that reported the builds.  See the
+<a href="#instr">instructions</a> for how to report a successful cross
+build.</p>
+
+<h2>Reports of Successful Cross Builds</h2>
+
+<table>
+
+<tr>
+<td>avr on i686-pc-cygwin</td>
+<td><a href="http://gcc.gnu.org/ml/gcc/2002-01/msg00239.html";>3.0.2</a></td>
+</tr>
+
+<tr>
+<td>mips-linux on x86</td>
+<td><a href="http://gcc.gnu.org/ml/gcc/2002-01/msg00079.html";>3.0.1</a></td>
+</tr>
+
+<tr>
+<td>mipsel-linux on x86</td>
+<td><a href="http://gcc.gnu.org/ml/gcc/2002-01/msg00079.html";>3.0.[123]</a></td>
+</tr>
+
+<tr>
+<td>sh-elf on sh-elf built on i386-linux</td>
+<td><a href="http://gcc.gnu.org/ml/gcc/2002-01/msg00168.html";>3.0.1</a></td>
+</tr>
+
+<tr>
+<td>sparc-sun-solaris2.8 on i686-pc-linux-gnu</td>
+<td>
+<a href="http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01252.html";>3.0.3</a></td>
+</tr>
+
+</table>
+
+<h2><a name="instr">Reporting Instructions</a></h2>
+
+<p>To add a new entry to this list, send a note to
+<a href="mailto:gcc@gcc.gnu.org";>gcc@gcc.gnu.org</a> indicating
+that you successfully built and installed a GCC cross compiler.
+Include the following information:</p>
+<ul>
+<li>Output from running <code><var>srcdir</var>/config.guess</code> on
+the target machine or, if that is not possible, a reasonable guess about
+what that would be.</li>
+<li>Output from running <code><var>srcdir</var>/config.guess</code> on
+the host machine.</li>
+<li>If the build machine is different from the host, output from running
+<code><var>srcdir</var>/config.guess</code> on the build machine.</li>
+<li>Output of <code>gcc -v</code> for your cross compiler.  This tells us
+which verison of GCC you built and the options you passed to configure,
+including which languages you enabled.</li>
+<li>Whether you used newlib or GNU libc.</li>
+<li>Whether you used cross GNU binutils and if so, which version.</li>
+<li>If the host and/or target is for GNU/Linux, also include:
+<ul>
+<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
+this information should be available from <code>/etc/issue</code>.</li>
+<li>The version of the Linux kernel, available from
+<code>uname --version</code> or <code>uname -a</code>.</li>
+<li>The version of glibc you used; for RPM-based systems like Red Hat,
+Mandrake, and SuSE type <code>rpm -q glibc</code> to get the glibc version,
+and on systems like Debian and Progeny use <code>dpkg -l libc6</code>.
+</ul>
+For other systems, you can include similar information if you think it is
+relevant.</li>
+<li>How much testing you did and how well your cross compiler seems to
+work.</li>
+<li>Anything else that would allow someone else to duplicate your build.</li>
+</ul>
+
+<p>If you have additional information about a build that has already been
+reported, include a link to the currently linked message in your mail and
+ask that your message replace it, thereby inserting your message at the
+beginning of the linked list of messages.</p>
+
+</body>
+</html>
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]