No description
Find a file
Vladimir Prus ef7723ebe7 * ser-mingw.c (pipe_windows_open)
(pipe_windows_read, pipe_windows_write): Declare
        variables at the top of the function.
2007-01-30 09:12:43 +00:00
bfd daily update 2007-01-29 23:00:10 +00:00
binutils * ar.c (print_contents, extract_file): Cast the return value 2007-01-25 15:40:22 +00:00
config 2007-01-14 H.J. Lu <hongjiu.lu@intel.com> 2007-01-14 15:39:41 +00:00
cpu
elfcpp Generate version information. 2006-12-06 00:02:36 +00:00
etc 2006-12-19 Paolo Bonzini <bonzini@gnu.org> 2006-12-19 14:01:25 +00:00
gas 2076-01-28 H.J. Lu <hongjiu.lu@intel.com> 2007-01-28 16:14:33 +00:00
gdb * ser-mingw.c (pipe_windows_open) 2007-01-30 09:12:43 +00:00
gold Don't emit symbols seen only in dynamic object, don't read duplicate 2006-12-06 06:28:56 +00:00
gprof * corefile.c (parse_error): New function. 2007-01-15 23:26:08 +00:00
include bfd/ 2007-01-16 14:56:32 +00:00
intl
ld * NEWS: Mention --vfp11-denorm-fix option. 2007-01-29 16:28:40 +00:00
libiberty * pex-unix.c (writeerr): Cast write result to void. 2007-01-12 02:21:52 +00:00
opcodes Move 2006 ChangeLog entries to ChangeLog-2006. 2007-01-09 14:29:31 +00:00
readline 2006-11-13 Denis Pilat <denis.pilat@st.com> 2006-11-13 09:33:30 +00:00
sim 2007-01-28 Manuel Lauss <slauss@resi.at> 2007-01-29 16:41:14 +00:00
texinfo
.cvsignore
ChangeLog 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 15:23:41 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2006-12-11 04:12:46 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2006-12-11 04:12:46 +00:00
configure 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 15:23:41 +00:00
configure.in 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 15:23:41 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2006-10-27 Jeff Johnston <jjohnstn@redhat.com> 2006-10-27 23:00:35 +00:00
COPYING.NEWLIB 2006-10-27 Jeff Johnston <jjohnstn@redhat.com> 2006-10-27 22:57:03 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 11:22:52 +00:00
Makefile.in 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 11:22:52 +00:00
Makefile.tpl 2007-01-11 Paolo Bonzini <bonzini@gnu.org> 2007-01-11 11:22:52 +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.