Binutils with MCST patches
Go to file
H.J. Lu 2955a517f3 Skip ld-elf/pr19162.d for arc target
* testsuite/ld-elf/pr19162.d: Skip arc target.
2016-03-01 08:11:51 -08:00
bfd Automatic date update in version.in 2016-03-01 00:00:09 +00:00
binutils Add ChangeLog entries for PR ld/19645 2016-02-26 06:44:03 -08:00
config Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
cpu epiphany/disassembler: Improve alignment of output. 2016-02-02 11:09:17 +00:00
elfcpp Remove typename from Mips64_rela_data 2016-01-12 12:08:06 -08:00
etc
gas [ARC] Local symbols relocation cleanup 2016-02-29 16:51:11 +01:00
gdb Fix output path for arm-disp-step.exp 2016-03-01 15:21:42 +00:00
gold Discard FDEs for zero-length address ranges. 2016-02-26 07:53:20 -08:00
gprof Regen configure 2016-01-17 12:28:14 +10:30
include Add ChangeLog entries for PR ld/19645 2016-02-26 06:44:03 -08:00
intl
ld Skip ld-elf/pr19162.d for arc target 2016-03-01 08:11:51 -08:00
libdecnumber
libiberty Sync libiberty with GCC. 2016-01-28 21:44:42 +01:00
opcodes Fix typo in print_insn_rl78_common function. 2016-03-01 10:52:24 +00:00
readline
sim sim: mips: fix prog_bfd usage 2016-02-05 20:27:25 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore Import changes made to files shared with the FSF GCC project. 2016-01-11 11:06:56 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
MAINTAINERS
Makefile.def Sync top-level Makefile.def with GCC 2016-01-12 08:34:40 -08:00
Makefile.in Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
Makefile.tpl Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
README
README-maintainer-mode
compile
config-ml.in
config.guess Import changes made to files shared with the FSF GCC project. 2016-01-11 11:06:56 +00:00
config.rpath
config.sub Import changes made to files shared with the FSF GCC project. 2016-01-11 11:06:56 +00:00
configure Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
configure.ac Sync top level files with gcc. 2016-02-10 10:54:29 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4 Sync top-level btool.m4 with GCC 2016-01-12 08:44:52 -08:00
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
src-release.sh fix gdb version parsing in src-release.sh 2016-01-17 10:01:55 +04:00
symlink-tree
ylwrap

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.