egcs/README (was: egcs-1.0.3a on mips-sgi-irix-6.3)

Gerald Pfeifer pfeifer@dbai.tuwien.ac.at
Tue Sep 1 07:24:00 GMT 1998


[ Please remove egcs@cygnus.com from replies ]

On Mon, 10 Aug 1998 Julian.Byrne@eng.monash.edu.au wrote:
> Suggestion: replace README in root directory with a pointer to the
> INSTALL directory. I followed the instructions in the current README
> and got an aborted install [...]

May I second this?  How about the following patch?

(If accepted, I'd strongly recommend to put it in 1.1 as well, that's why
I'm also directly sending it to you, Jeff. Or is it too late, already?)

Gerald

Tue Sep  1 16:23:11 1998  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* README: Remove installation instructions and refer to the
	INSTALL directory instead.

Index: README
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/README,v
retrieving revision 1.2
diff -c -3 -p -r1.2 README
*** README	1998/04/03 16:21:54	1.2
--- README	1998/09/01 14:20:50
***************
*** 3,42 ****
  This directory contains various GNU compilers, assemblers, linkers, 
  debuggers, etc., plus their support routines, definitions, and documentation.
  
- If you are receiving this as part of a GDB release, see the file gdb/README.
- If with a binutils release, see binutils/README;  if with a libg++ release,
- see libg++/README, etc.  That'll give you info about this
- package -- supported targets, how to use it, how to report bugs, etc.
  
! It is now possible to automatically configure and build a variety of
! tools with one command.  To build all of the tools contained herein,
! run the ``configure'' script here, e.g.:
  
- 	./configure 
- 	make
- 
- To install them (by default in /usr/local/bin, /usr/local/lib, etc),
- then do:
- 	make install
- 
- (If the configure script can't determine your type of computer, give it
- the name as an argument, for instance ``./configure sun4''.  You can
- use the script ``config.sub'' to test whether a name is recognized; if
- it is, config.sub translates it to a triplet specifying CPU, vendor,
- and OS.)
- 
- If you have more than one compiler on your system, it is often best to
- explicitly set CC in the environment before running configure, and to
- also set CC when running make.  For example (assuming sh/bash/ksh):
- 
- 	CC=gcc ./configure
- 	make
- 
- A similar example using csh:
- 
- 	setenv CC gcc
- 	./configure
- 	make
  
  Much of the code and documentation enclosed is copyright by
  the Free Software Foundation, Inc.  See the file COPYING or
--- 3,12 ----
  This directory contains various GNU compilers, assemblers, linkers, 
  debuggers, etc., plus their support routines, definitions, and documentation.
  
  
! Check the INSTALL directory for detailed configuration and installation
! instructions.
  
  
  Much of the code and documentation enclosed is copyright by
  the Free Software Foundation, Inc.  See the file COPYING or







More information about the Gcc mailing list