Binutils with MCST patches
Go to file
Kaz Kojima f2e349f91a * ldlang.c (load_symbols): Set as_needed and add_needed according
to the corresponding script's fields while processing it.
2006-04-07 07:03:51 +00:00
bfd * elf32-m32c.c (m32c_elf_relocate_section): Generate a symbol for 2006-04-07 01:08:34 +00:00
binutils 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
config 2006-02-14 Paolo Bonzini <bonzini@gnu.org> 2006-02-14 09:22:15 +00:00
contrib
cpu * m32c.cpu (Bit3-S): New. 2006-03-14 04:20:53 +00:00
etc 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
gas PR 2512. 2006-04-07 06:40:57 +00:00
gdb *** empty log message *** 2006-04-07 00:00:02 +00:00
gprof 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
include bfd/ 2006-04-06 18:52:46 +00:00
intl 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
ld * ldlang.c (load_symbols): Set as_needed and add_needed according 2006-04-07 07:03:51 +00:00
libiberty merge from gcc 2006-04-07 00:01:28 +00:00
mmalloc
opcodes 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
readline * histfile.c (read_history_range): Remove '\r' character from 2006-03-21 14:58:24 +00:00
sim * sim/cris/hw: New directory for subdirectories with tests. 2006-04-03 03:05:00 +00:00
texinfo
.cvsignore
ChangeLog 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
compile
config-ml.in
config.guess Sync top level config files from the master config repository 2006-01-16 17:34:37 +00:00
config.sub Sync top level config files from the master config repository 2006-01-16 17:34:37 +00:00
configure 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
configure.in 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
gettext.m4
install-sh
libtool.m4 PR binutils/1990 2005-12-27 16:37:57 +00:00
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh 2006-03-01 H.J. Lu <hongjiu.lu@intel.com> 2006-03-01 17:40:34 +00:00
MAINTAINERS Update information about: config-ml.in; makefile.vms; mkdep; setup.com; 2006-03-01 10:25:01 +00:00
Makefile.def 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
Makefile.in 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
Makefile.tpl 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.