No description
Find a file
Adam Fedor 1abf022c0c * objc-lang.c (CONVERT_FUNCPTR): Remove macro
(find_implementation_from_class): Replace it with the standard
case i.e. do nothing.
2003-05-30 02:45:21 +00:00
bfd daily update 2003-05-30 00:00:04 +00:00
binutils 2003-05-20 Michal Ludvig <mludvig@suse.cz> 2003-05-20 14:37:46 +00:00
config * acinclude.m4: Accept i[3456789]86 for machine type. 2003-05-19 18:11:58 +00:00
contrib
cpu 2003-05-02 Andrew Cagney <cagney@redhat.com> 2003-05-03 00:44:23 +00:00
etc Replace i[3456]86 with i[3-7]86 2003-05-16 16:30:27 +00:00
gas Add i386-*-freebsd* entry. 2003-05-29 18:17:55 +00:00
gdb * objc-lang.c (CONVERT_FUNCPTR): Remove macro 2003-05-30 02:45:21 +00:00
gprof
include 2003-05-23 Jason Eckhardt <jle@rice.edu> 2003-05-24 04:22:23 +00:00
intl
ld * configure.host (*-*-netbsd*): Set HOSTING_CRT0 and HOSTING_LIBS 2003-05-29 17:38:52 +00:00
libiberty * config.table: Accept i[345867]86 variant. 2003-05-20 02:49:35 +00:00
mmalloc
opcodes 2003-05-23 Jason Eckhardt <jle@rice.edu> 2003-05-24 04:22:23 +00:00
readline * aclocal.m4: Don't add wcwidth.o if we don't have wchar.h. 2003-05-27 23:29:47 +00:00
sim Use $(SHELL) whenever we invoke move-if-change. 2003-05-16 07:11:43 +00:00
texinfo
.cvsignore
ChangeLog Import patch to add FreeBSD support. 2003-05-29 14:02:04 +00:00
config-ml.in 2003-05-05 H.J. Lu <hjl@gnu.org> 2003-05-05 21:35:08 +00:00
config.guess 2003-05-13 Andreas Jaeger <aj@suse.de> 2003-05-13 12:09:10 +00:00
config.if
config.sub 2003-05-13 Andreas Jaeger <aj@suse.de> 2003-05-13 12:09:10 +00:00
configure * configure.in: Use curly braces in the definition of tooldir. 2003-05-22 02:47:53 +00:00
configure.in 2003-05-20 Maciej W. Rozycki <macro@ds2.pg.gda.pl> 2003-05-20 21:09:44 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB 2003-05-28 Jeff Johnston <jjohnstn@redhat.com> 2003-05-28 17:51:42 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig Import patch to add FreeBSD support. 2003-05-29 14:02:04 +00:00
ltmain.sh
MAINTAINERS 2003-05-02 Andrew Cagney <cagney@redhat.com> 2003-05-03 00:44:23 +00:00
Makefile.def
Makefile.in * Makefile.tpl: Make maybe-check-gcc .PHONY. 2003-05-28 19:16:29 +00:00
Makefile.tpl * Makefile.tpl: Make maybe-check-gcc .PHONY. 2003-05-28 19:16:29 +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
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.