Binutils with MCST patches
Go to file
2007-09-01 00:00:34 +00:00
bfd daily update 2007-09-01 00:00:09 +00:00
binutils 2007-08-31 H.J. Lu <hongjiu.lu@intel.com> 2007-08-31 15:06:11 +00:00
config Move changelog 2007-08-30 20:22:12 +00:00
cpu
elfcpp
etc * standards.texi: Import 22 July 2007 version. 2007-08-13 09:45:22 +00:00
gas gas/testsuite/ 2007-08-31 18:48:29 +00:00
gdb *** empty log message *** 2007-09-01 00:00:34 +00:00
gold Any symbol which is in both a regular object and a dynamic object 2007-08-29 05:48:24 +00:00
gprof Updated Finnish translation 2007-08-30 13:30:59 +00:00
include merge from gcc 2007-08-31 20:20:49 +00:00
intl
ld * ldlang.c (lang_map): Increment lang_statement_iteration so that DEFINED() expressions are correctly computed. 2007-08-31 14:46:55 +00:00
libiberty merge from gcc 2007-08-31 20:20:49 +00:00
opcodes 2007-08-31 H.J. Lu <hongjiu.lu@intel.com> 2007-08-31 20:55:13 +00:00
readline
sim * compare_igen_models: Change license to GPL version 3. 2007-08-28 16:08:00 +00:00
texinfo
.cvsignore
ChangeLog Move changelog 2007-08-30 20:22:12 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2007-08-29 15:23:21 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2007-08-29 15:23:21 +00:00
configure Bring over from the GCC tree: 2007-08-21 04:15:07 +00:00
configure.ac Bring over from the GCC tree: 2007-08-21 04:15:07 +00:00
COPYING
COPYING3 * COPYING3: New file. Contains version 3 of the GNU General Public License. 2007-07-17 13:50:23 +00:00
COPYING3.LIB * COPYING3: New file. Contains version 3 of the GNU General Public License. 2007-07-17 13:50:23 +00:00
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4 2007-07-05 H.J. Lu <hongjiu.lu@intel.com> 2007-07-05 17:57:04 +00:00
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def * Makefile.def (STAGE2_CFLAGS, STAGE3_CFLAGS, STAGE4_CFLAGS): 2007-08-17 00:03:44 +00:00
Makefile.in 2007-08-18 Paul Brook <paul@codesourcery.com> 2007-08-18 15:19:10 +00:00
Makefile.tpl 2007-08-18 Paul Brook <paul@codesourcery.com> 2007-08-18 15:19:10 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release * src-release (DEVO_SUPPORT): Add COPYING3 and COPYING3.LIB. 2007-08-12 19:05:42 +00:00
symlink-tree
ylwrap

		   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.