Binutils with MCST patches
Go to file
Stephane Carrez a66c0f2c3b * emulparams/m68hc12elfb.sh (EEPROM_MEMORY): Define.
* emulparams/m68hc11elfb.sh (EEPROM_MEMORY): Define.
	* emulparams/m68hc11elf.sh (EEPROM_SIZE): Define.
	(EEPROM_START_ADDR): Define.
	(EEPROM_MEMORY): Define.
	* emulparams/m68hc12elf.sh: Likewise.
	* scripttempl/elfm68hc11.sc: Handle .eeprom section; handle .softregs
	section to put soft registers in .page0.
	* scripttempl/elfm68hc12.sc: Likewise but put soft registers in bss.
2002-06-29 10:33:45 +00:00
bfd daily update 2002-06-29 00:00:06 +00:00
binutils Rescind Tom Rix's maintainerships. 2002-06-26 15:26:52 +00:00
config Revoke adding mh-s390xpic. Doesn't make any sense because it is not 2002-06-11 13:34:24 +00:00
etc Import latest version of texi2pod.pl from FSF GCC sources. 2002-06-11 15:34:33 +00:00
gas * config/tc-m68hc11.h (ELF_TC_SPECIAL_SECTIONS): New sections 2002-06-29 10:32:34 +00:00
gdb *** empty log message *** 2002-06-29 00:00:32 +00:00
gprof Do not attempt to create a .gmo file if the sources are read-only. 2002-05-02 08:15:00 +00:00
include merge from gcc 2002-06-25 01:03:52 +00:00
intl
ld * emulparams/m68hc12elfb.sh (EEPROM_MEMORY): Define. 2002-06-29 10:33:45 +00:00
libiberty merge from gcc 2002-06-22 13:31:20 +00:00
mmalloc
opcodes 2002-06-18 Dave Brolley <brolley@redhat.com> 2002-06-18 21:21:05 +00:00
readline
sim 2002-06-24 Richard Sandiford <rsandifo@redhat.com> 2002-06-24 13:26:07 +00:00
texinfo
.cvsignore
ChangeLog 2002-06-24 Ben Elliston <bje@redhat.com> 2002-06-24 17:41:28 +00:00
config-ml.in * config-ml.in: Propogate DESTDIR also. 2002-05-31 19:30:32 +00:00
config.guess * config.guess: Update to 2002-05-22 version. 2002-05-22 18:36:13 +00:00
config.if
config.sub 2002-06-18 Dave Brolley <brolley@redhat.com> 2002-06-18 21:09:34 +00:00
configure * Makefile.in: Replace HOST_PREFIX, HOST_PREFIX_1 with BUILD_PREFIX, 2002-05-31 20:09:45 +00:00
configure.in 2002-06-24 Ben Elliston <bje@redhat.com> 2002-06-24 17:41:28 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2002-05-07 Jeff Johnston <jjohnstn@redhat.com> 2002-05-07 17:52:36 +00:00
COPYING.NEWLIB
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in 2002-06-24 Ben Elliston <bje@redhat.com> 2002-06-24 17:41:28 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
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.