Go to file
J"orn Rennecke 4dff12bfa2 sh.md (attribute "type"): Add nil.
* sh.md (attribute "type"): Add nil.
        (movsi_ie): y/y alternative is type nil.
        (movsf_ie): Replace ry/yr/X alternative by r/y/X , y/r/X and y/y/X
        alternatives.
        (movsf_ie+1): Delete.

From-SVN: r16575
1997-11-19 00:36:12 +00:00
config More stuff from Uli. 1997-09-16 10:11:13 -06:00
etc aclocal.m4: Substitute INSTALL. 1997-10-07 16:26:56 -06:00
gcc sh.md (attribute "type"): Add nil. 1997-11-19 00:36:12 +00:00
include Initial revision 1997-08-21 18:57:35 -04:00
libiberty * Makefile.in (CFILES): Add pexecute.c. 1997-10-28 23:39:04 -07:00
libio * stdstrbufs.cc (DEF_STDFILE): Use STD_VTABLE. 1997-11-18 09:53:45 -07:00
libstdc++ * Makefile.in (SHLIB): Build with CC instead of CXX. 1997-11-16 22:41:36 -07:00
texinfo Makefile.in (install targets): Add a dummy target for sunos make. 1997-10-31 09:38:44 -07:00
xiberty Initial revision 1997-08-21 18:57:35 -04:00
.cvsignore * .cvsignore (*-install): Remove. 1997-09-04 09:49:02 -06:00
ChangeLog * Makefile.in: check-target-libio depends on all-target-libstdc++. 1997-10-27 15:04:45 -05:00
config-ml.in Initial revision 1997-08-21 18:57:35 -04:00
config.guess Make the gcc config.guess exec the toplevel config.guess. 1997-08-27 16:20:52 -07:00
config.sub * config.sub: Accept 'amigados' for backward compatability. 1997-09-10 15:18:25 -06:00
configure Uli's libio/libstdc++ patches. 1997-09-16 10:01:55 -06:00
configure.in Uli's libio/libstdc++ patches. 1997-09-16 10:01:55 -06:00
COPYING Initial revision 1997-08-21 18:57:35 -04:00
COPYING.LIB Initial revision 1997-08-21 18:57:35 -04:00
install-sh Initial revision 1997-08-21 18:57:35 -04:00
ltconfig Initial revision 1997-08-21 18:57:35 -04:00
ltmain.sh Initial revision 1997-08-21 18:57:35 -04:00
Makefile.in * Makefile.in: check-target-libio depends on all-target-libstdc++. 1997-10-27 15:04:45 -05:00
missing Initial revision 1997-08-21 18:57:35 -04:00
mkinstalldirs Initial revision 1997-08-21 18:57:35 -04:00
move-if-change Initial revision 1997-08-21 18:57:35 -04:00
mpw-build.in Initial revision 1997-08-21 18:57:35 -04:00
mpw-config.in Initial revision 1997-08-21 18:57:35 -04:00
mpw-configure Initial revision 1997-08-21 18:57:35 -04:00
mpw-install ignored by import 1997-08-21 19:14:36 -04:00
mpw-README Initial revision 1997-08-21 18:57:35 -04:00
README Initial revision 1997-08-21 18:57:35 -04:00
symlink-tree Initial revision 1997-08-21 18:57:35 -04:00
ylwrap Initial revision 1997-08-21 18:57:35 -04:00

		   README for GNU development tools

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
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.