PATCH: Do not install specs file

[Mark Mitchell]

I checked in the attached variant of my original patch, which
addresses Alexandre's comments about the fact that we still need to
install the specs file on platforms that define SPECS.  (There is only
one such platform at this point; hopefully that can be reduced to
zero...)

The second hunk is a patch for wwwdocs to mention this change.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

2004-12-20  Mark Mitchell  <mark@codesourcery.com>

	* Makefile.in (install-common): Do not install the specs file
	unless SPECS is defined.

Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/Makefile.in,v
retrieving revision 1.1435
diff -c -5 -p -r1.1435 Makefile.in
*** Makefile.in	19 Dec 2004 04:42:07 -0000	1.1435
--- Makefile.in	20 Dec 2004 20:47:49 -0000
*************** install-common: native $(EXTRA_PARTS) la
*** 3234,3249 ****
  	    rm -f $(DESTDIR)$(libsubdir)/$$file; \
  	    $(INSTALL_DATA) $$file $(DESTDIR)$(libsubdir)/$$file; \
  	    chmod a-x $(DESTDIR)$(libsubdir)/$$file; \
  	  else true; fi; \
  	done
! # Don't mess with specs if it doesn't exist yet.
! 	-if [ -f specs ] ; then \
! 	  rm -f $(DESTDIR)$(libsubdir)/specs; \
! 	  $(INSTALL_DATA) $(SPECS) $(DESTDIR)$(libsubdir)/specs; \
! 	  chmod a-x $(DESTDIR)$(libsubdir)/specs; \
! 	fi
  # Install protoize if it was compiled.
  	-if [ -f protoize$(exeext) ]; then \
  	  rm -f $(DESTDIR)$(bindir)/$(PROTOIZE_INSTALL_NAME)$(exeext); \
  	  $(INSTALL_PROGRAM) protoize$(exeext) $(DESTDIR)$(bindir)/$(PROTOIZE_INSTALL_NAME)$(exeext); \
  	  rm -f $(DESTDIR)$(bindir)/$(UNPROTOIZE_INSTALL_NAME)$(exeext); \
--- 3234,3256 ----
  	    rm -f $(DESTDIR)$(libsubdir)/$$file; \
  	    $(INSTALL_DATA) $$file $(DESTDIR)$(libsubdir)/$$file; \
  	    chmod a-x $(DESTDIR)$(libsubdir)/$$file; \
  	  else true; fi; \
  	done
! # Remove any specs file installed by a previous version of GCC.  
! 	rm -f $(DESTDIR)$(libsubdir)/specs
! ifneq ($(SPECS),specs)
! # In general, we no longer install the specs file because its presence
! # makes the driver slower, and because people who need it can recreate
! # it by using -dumpspecs.
! #
! # However, in the case that the target has defined SPECS, then we must
! # install the file.  It may be that the installed specs file is
! # different from that built into the driver.
! 	$(INSTALL_DATA) $(SPECS) $(DESTDIR)$(libsubdir)/specs
! 	chmod a-x $(DESTDIR)$(libsubdir)/specs
! endif
  # Install protoize if it was compiled.
  	-if [ -f protoize$(exeext) ]; then \
  	  rm -f $(DESTDIR)$(bindir)/$(PROTOIZE_INSTALL_NAME)$(exeext); \
  	  $(INSTALL_PROGRAM) protoize$(exeext) $(DESTDIR)$(bindir)/$(PROTOIZE_INSTALL_NAME)$(exeext); \
  	  rm -f $(DESTDIR)$(bindir)/$(UNPROTOIZE_INSTALL_NAME)$(exeext); \
Index: gcc-4.0/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.22
diff -c -5 -p -r1.22 changes.html
*** gcc-4.0/changes.html	3 Dec 2004 05:22:14 -0000	1.22
--- gcc-4.0/changes.html	20 Dec 2004 20:49:41 -0000
***************
*** 55,64 ****
--- 55,69 ----
  	ASCII English-language messages should set
  	<code>LC_ALL=C</code>.  See <a
  	href="http://www.cl.cam.ac.uk/~mgk25/ucs/quotes.html">Markus
  	Kuhn's explanation of Unicode quotation marks</a> for more
  	information.</li>
+    <li>The <code>specs</code> file is no longer installed on most
+ 	platforms.  Most users will be totally unaffected.  However,
+ 	if you are accustomed to editing the specs file yourself, you
+ 	will now have to use the <code>-dumpspecs</code> option to
+ 	generate the specs file, and then edit the resulting file.</li> 
    </ul>
  
  <h2>General Optimizer Improvements</h2>
  
    <ul>