You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sandy 99da0f2c72 pl286 release code 4 years ago
..
bfd pl286 release code 4 years ago
binutils pl286 release code 4 years ago
config pl286 release code 4 years ago
cpu pl286 release code 4 years ago
elfcpp pl286 release code 4 years ago
etc pl286 release code 4 years ago
gas pl286 release code 4 years ago
gold pl286 release code 4 years ago
gprof pl286 release code 4 years ago
include pl286 release code 4 years ago
intl pl286 release code 4 years ago
ld pl286 release code 4 years ago
libiberty pl286 release code 4 years ago
opcodes pl286 release code 4 years ago
texinfo pl286 release code 4 years ago
.cvsignore pl286 release code 4 years ago
COPYING pl286 release code 4 years ago
COPYING.LIB pl286 release code 4 years ago
COPYING.LIBGLOSS pl286 release code 4 years ago
COPYING.NEWLIB pl286 release code 4 years ago
COPYING3 pl286 release code 4 years ago
COPYING3.LIB pl286 release code 4 years ago
ChangeLog pl286 release code 4 years ago
MAINTAINERS pl286 release code 4 years ago
Makefile.def pl286 release code 4 years ago
Makefile.in pl286 release code 4 years ago
Makefile.tpl pl286 release code 4 years ago
README pl286 release code 4 years ago
README-maintainer-mode pl286 release code 4 years ago
README.google pl286 release code 4 years ago
compile pl286 release code 4 years ago
config-ml.in pl286 release code 4 years ago
config.guess pl286 release code 4 years ago
config.rpath pl286 release code 4 years ago
config.sub pl286 release code 4 years ago
configure pl286 release code 4 years ago
configure.ac pl286 release code 4 years ago
depcomp pl286 release code 4 years ago
install-sh pl286 release code 4 years ago
libtool.m4 pl286 release code 4 years ago
ltgcc.m4 pl286 release code 4 years ago
ltmain.sh pl286 release code 4 years ago
ltoptions.m4 pl286 release code 4 years ago
ltsugar.m4 pl286 release code 4 years ago
ltversion.m4 pl286 release code 4 years ago
lt~obsolete.m4 pl286 release code 4 years ago
makefile.vms pl286 release code 4 years ago
missing pl286 release code 4 years ago
mkdep pl286 release code 4 years ago
mkinstalldirs pl286 release code 4 years ago
move-if-change pl286 release code 4 years ago
setup.com pl286 release code 4 years ago
src-release.sh pl286 release code 4 years ago
symlink-tree pl286 release code 4 years ago
ylwrap pl286 release code 4 years ago

README

		   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.