This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
web page updates: remove obsolete "egcs" mentions (fwd)
- To: Joe Buck <jbuck at welsh-buck dot org>
- Subject: web page updates: remove obsolete "egcs" mentions (fwd)
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Fri, 17 Dec 1999 21:02:18 +0100 (MET)
- cc: gcc-patches at gcc dot gnu dot org
This (apparently) bounced from the gcc.gnu.org machine and dropped
into my DEVNULL.spam folder as well because the IP you use is listed
by MAPS DUL.
Sorry Joe!
I had a look at the patches. These are fine and I'll install them shortly.
(Actually I have not checked all links, but my next link check run will
detect any broken links anyway...)
Thanks a lot!
Gerald
---------- Forwarded message ----------
Received: from welsh-buck.org (IDENT:jbuck@dynamic60.pm05.san-jose.best.com [209.24.165.60])
by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id IAA11148
for <pfeifer@dbai.tuwien.ac.at>; Fri, 17 Dec 1999 08:19:21 +0100 (MET)
Received: (from jbuck@localhost)
by welsh-buck.org (8.8.5/8.8.5) id XAA02330;
Thu, 16 Dec 1999 23:19:00 -0800
Date: Thu, 16 Dec 1999 23:19:00 -0800
From: Joe Buck <jbuck@welsh-buck.org>
Message-Id: <199912170719.XAA02330@welsh-buck.org>
To: gcc-patches@gcc.gnu.org
Subject: web page updates: remove obsolete "egcs" mentions
Cc: pfeifer@dbai.tuwien.ac.at
Hi,
Here's a patch to take out some leftover egcs mentions in our web pages.
Gerald, can you check this and install?
Joe (using my home account)
Index: checkin.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/checkin.html,v
retrieving revision 1.11
diff -u -r1.11 checkin.html
--- checkin.html 1999/07/17 09:15:11 1.11
+++ checkin.html 1999/12/17 07:13:36
@@ -1,18 +1,18 @@
<html>
<head>
-<title>Checking in changes to egcs </title>
+<title>Checking in changes to GCC </title>
</head>
<body>
-<h1 align="center">Checking in changes to egcs </h1>
+<h1 align="center">Checking in changes to GCC</h1>
<p>This page is meant to give a very brief outline of the policies and
-procedures for checking in files to egcs for those folks with write
+procedures for checking in files to GCC for those folks with write
access to the repository.
<hr>
<h2>Write access policies</h2>
-<p>The egcs project grants some developers various levels of write access
-to the egcs master sources. CVS doesn't provide fine grained control over
+<p>The GCC project grants some developers various levels of write access
+to the GCC master sources. CVS doesn't provide fine grained control over
access to the repository; therefore, we depend on each developer to follow
the appropriate policies.
@@ -31,11 +31,11 @@
but who do not "own" any particular piece of code. People with write after
approval need to submit their patches to the list; once the patches have
been approved by the appropriate maintainers the patches may be checked into
- the egcs sources.
+ the GCC sources.
</ul>
<p>The list of folks with write access to the repository can be found in the
-<tt>MAINTAINERS</tt> file in the egcs distribution.
+<tt>MAINTAINERS</tt> file in the GCC distribution.
<hr>
<p>Also note that fixes for obvious typos in ChangeLog files, docs, web
@@ -78,7 +78,7 @@
log message via the "<tt>-m</tt>" argument to commit, or wait for the
editor window to appear and enter the log message in the editor window.
-<p>After exiting the editor, CVS will connect to the egcs cvs server and
+<p>After exiting the editor, CVS will connect to the GCC cvs server and
check in your changes. When your prompt returns the checkin is finished.
A message will be sent to the "<tt>gcc-cvs</tt>" mailing list (when
set up) indicating that a change was made. CVS will provide a message
@@ -88,7 +88,7 @@
<h2> Example check-in session </h2>
<p>Here's an actual check-in session for a patch John Carr recently sent
-to the egcs list. This was the <tt>ChangeLog</tt> for his change:
+to the GCC list. This was the <tt>ChangeLog</tt> for his change:
<blockquote>
<pre>
@@ -269,7 +269,7 @@
<p>And that's it!
<hr>
-<i>Last modified on July 13, 1999.</i>
+<i>Last modified on December 16, 1999.</i>
</body>
</html>
Index: cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.14
diff -u -r1.14 cvswrite.html
--- cvswrite.html 1999/10/10 13:48:42 1.14
+++ cvswrite.html 1999/12/17 07:13:45
@@ -23,7 +23,7 @@
in cluttering up the developers list with keys.
<p>Once we have this information we will set up an account on
-egcs.cygnus.com and inform you by mail. At this point you should be
+gcc.gnu.org and inform you by mail. At this point you should be
able to check out a tree with CVS and add yourself to the MAINTAINERS
file to test write access.
@@ -35,10 +35,10 @@
the command
<blockquote><code>
-cvs -z 9 -d :ext:username@egcs.cygnus.com:/cvs/gcc co egcs
+cvs -z 9 -d :ext:username@gcc.gnu.org:/cvs/gcc co egcs
</code></blockquote>
-where <code>username</code> is your user name at egcs.cygnus.com.
+where <code>username</code> is your user name at gcc.gnu.org.
This will check out a new CVS tree that you should be able to work with
in the normal fashion, including committing changes.
@@ -47,7 +47,7 @@
all the "Root" files in the local tree with the following contents:
<blockquote><code>
-username@egcs.cygnus.com:/cvs/gcc
+username@gcc.gnu.org:/cvs/gcc
</code></blockquote>
@@ -61,7 +61,7 @@
starts. To avoid messages about (lack of) X11 forwarding, put in your
<samp>$HOME/.ssh/config</samp> and entry like:
<blockquote><code>
-Host egcs.cygnus.com<br>
+Host gcc.gnu.org<br>
ForwardX11 no
</code></blockquote>
@@ -71,9 +71,9 @@
automatically be checked out into the web server's data area.
<hr>
-<i>Last modified on July 14, 1999.</i>
+<i>Last modified on December 16, 1999.</i>
<hr>
-<a href="/">Return to the egcs home page</a>
+<a href="/">Return to the GCC home page</a>
</body>
</html>
Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.151
diff -u -r1.151 faq.html
--- faq.html 1999/11/25 20:04:38 1.151
+++ faq.html 1999/12/17 07:14:02
@@ -194,7 +194,7 @@
The manual can also be read using `<i>M-x <tt>info</tt></i>' in Emacs, or if
the GNU <tt>info</tt> program is installed on your system by `<tt>info --node
"(gcc)Bugs"</tt>'. Or see the file
-<a href="http://egcs.cygnus.com/cgi-bin/cvsweb.cgi/~checkout~/egcs/gcc/BUGS?content-type=text/plain&only_with_tag=HEAD">BUGS</a>
+<a href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/~checkout~/egcs/gcc/BUGS?content-type=text/plain&only_with_tag=HEAD">BUGS</a>
included with the GCC source code.</p>
<p>Before you report a bug for the <em>C++ compiler</em>, please check
@@ -475,7 +475,7 @@
<p>If you get a message about unable to find "standard.exp" when trying to
run the GCC testsuites, then your dejagnu is too old to run the GCC tests.
You will need to get a newer version of dejagnu; we've made a
-<a href="ftp://egcs.cygnus.com/pub/egcs/infrastructure/dejagnu-19981026.tar.gz">
+<a href="ftp://gcc.gnu.org/pub/egcs/infrastructure/dejagnu-19981026.tar.gz">
dejagnu snapshot</a> available until a new version of dejagnu can be released.</p>
<hr>
@@ -630,7 +630,7 @@
The 2.0.x kernels are to be built only with
gcc 2.7.2. They use certain <code>asm</code> constructs which are
incorrect, but (by accident) happen to work with gcc 2.7.2. If you
-insist on building 2.0.x kernels with egcs, you may be interested in
+insist on building 2.0.x kernels with later versions of GCC (or egcs), you may be interested in
this <a href="http://www.suse.de/~florian/kernel+egcs.html">patch</a>
which fixes some of the asm problems. You will also want to change
asm constructs to <a href="#asmclobber">avoid clobbering their input
@@ -975,7 +975,7 @@
<p>If you do need libg++ you can get a libg++ release that works with
GCC from <a
-href="ftp://egcs.cygnus.com/pub/egcs/infrastructure/">ftp://egcs.cygnus.com/pub/egcs/infrastructure/</a>.
+href="ftp://gcc.gnu.org/pub/egcs/infrastructure/">ftp://gcc.gnu.org/pub/egcs/infrastructure/</a>.
Note that the 2.8.2 snapshot pre-dates the 2.8.1.2 release.</p>
<hr>
@@ -1007,8 +1007,8 @@
<p>Autoconf is available from
<a href="http://sourceware.cygnus.com/autoconf/">
http://sourceware.cygnus.com/autoconf/</a>; have a look at
-<a href="ftp://egcs.cygnus.com/pub/egcs/infrastructure/">
-ftp://egcs.cygnus.com/pub/egcs/infrastructure/</a> for the other packages.
+<a href="ftp://gcc.gnu.org/pub/egcs/infrastructure/">
+ftp://gcc.gnu.org/pub/egcs/infrastructure/</a> for the other packages.
</p>
<hr>
@@ -1097,7 +1097,7 @@
package.</p>
<p>Unfortunately, GNU as does not support all platforms supported by
-egcs, so you may have to use an experimental work-around: the
+GCC, so you may have to use an experimental work-around: the
<tt>-fsquangle</tt> option, that enables compression of symbol names.</p>
<p>Note that this option is still under development, and subject to
@@ -1108,7 +1108,7 @@
<p>This option can be enabled by default by initializing
`flag_do_squangling' with `1' in `gcc/cp/decl2.c' (it is not
-initialized by default), then rebuilding egcs and any C++ libraries.</p>
+initialized by default), then rebuilding GCC and any C++ libraries.</p>
<hr>
<h2><a name="gperf">When building from CVS sources, I see 'gperf:
@@ -1116,10 +1116,10 @@
</a></h2>
<p>The current version of gperf (v2.7) does not support the -F flag
-which is used when building egcs from CVS sources. You will need to
+which is used when building GCC from CVS sources. You will need to
obtain a patch for gperf and rebuild the program; this patch is available
-at <a href="ftp://egcs.cygnus.com/pub/egcs/infrastructure">
-ftp://egcs.cygnus.com/pub/egcs/infrastructure/</a></p>
+at <a href="ftp://gcc.gnu.org/pub/egcs/infrastructure">
+ftp://gcc.gnu.org/pub/egcs/infrastructure/</a></p>
<p>Patches for other tools, particularly autoconf, may also be necessary
if you're building from CVS sources. Please see the
@@ -1129,7 +1129,7 @@
<p>These patched utilities should <strong>only</strong> be required if
you are building from CVS sources. For example, gperf is used to
generate C code for a perfect hash function given an input file.
-Distributions of egcs already contain the generated C code, while the
+Distributions of GCC already contain the generated C code, while the
CVS sources will provide only the gperf input file. So gperf should
only be necessary if you are building anything obtained from CVS.</p>
@@ -1139,7 +1139,7 @@
<p>The ISO C++ Standard specifies that all virtual methods of a class
that are not pure-virtual must be defined, but does not require any
diagnostic for violations of this rule [class.virtual]/8. Based on
-this assumption, egcs will only emit the implicitly defined
+this assumption, GCC will only emit the implicitly defined
constructors, the assignment operator, the destructor and the virtual
table of a class in the translation unit that defines its first such
non-inline method.</p>
Index: spam.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/spam.html,v
retrieving revision 1.2
diff -u -r1.2 spam.html
--- spam.html 1999/03/18 00:13:46 1.2
+++ spam.html 1999/12/17 07:14:10
@@ -5,7 +5,7 @@
<body>
<h1 align="center">Dealing with SPAM</h1>
-<p>Occasionally some bozo decides to spam the egcs mailing lists. While we
+<p>Occasionally some bozo decides to spam the GCC mailing lists. While we
wish this would not happen, it is a fact of life on an open list (we do not
want to run a list where only members can post).