Red Hat's newlib C library with support for Jehanne
Go to file
Christopher Faylor 149965f73c update comment 2002-05-27 02:06:16 +00:00
config * acinclude.m4: Allow for PWDCMD to override hardcoded pwd. 2002-05-22 21:06:53 +00:00
etc * fdl.texi: New file. 2002-02-28 03:34:36 +00:00
include * ia64.h: Use #include "" instead of <> for local header files. 2002-05-25 12:53:48 +00:00
libgloss * libnosys/acconfig.h (HAVE_SECTION_ATTRIBUTES): New macro. 2002-05-11 20:48:04 +00:00
newlib 2002-05-24 Jeff Johnston <jjohnstn@redhat.com> 2002-05-24 23:44:39 +00:00
texinfo * standards.texi: Import February 14, 2002 version. 2002-02-27 02:13:36 +00:00
winsup update comment 2002-05-27 02:06:16 +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 2002-02-04 Jeff Johnston <jjohnstn@redhat.com> 2002-02-05 00:29:31 +00:00
ChangeLog * config.guess: Update to 2002-05-22 version. 2002-05-22 18:36:13 +00:00
MAINTAINERS * MAINTAINERS: Update dejagnu/ 2002-04-07 19:17:07 +00:00
Makefile.in Allow for PWDCMD to override hardcoded pwd. 2002-05-22 09:21:32 +00:00
README
README-maintainer-mode Add note about inability to use "make distclean" in maintainer mode. 2001-03-23 18:06:17 +00:00
config-ml.in Allow for PWDCMD to override hardcoded pwd. 2002-05-22 09:21:32 +00:00
config.guess * config.guess: Update to 2002-05-22 version. 2002-05-22 18:36:13 +00:00
config.if 2001-05-14 H.J. Lu <hjl@gnu.org> 2001-05-14 16:40:49 +00:00
config.sub * config.guess: Update to 2002-05-22 version. 2002-05-22 18:36:13 +00:00
configure Allow for PWDCMD to override hardcoded pwd. 2002-05-22 09:21:32 +00:00
configure.in Allow for PWDCMD to override hardcoded pwd. 2002-05-22 09:21:32 +00:00
djunpack.bat
gettext.m4 * gettext.m4: Test po/POTFILES.in exists before trying to read. 2001-10-03 01:46:25 +00:00
install-sh
libtool.m4 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:30 +00:00
ltcf-c.sh 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:30 +00:00
ltcf-cxx.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-gcj.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltconfig 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:30 +00:00
ltmain.sh * ltmain.sh (relink_command): Fix typo in previous change. 2002-03-16 14:43:09 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-README
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
setup.com
symlink-tree gcc adopts symlink-tree, refer more to libiberty. 2001-12-05 10:07:09 +00:00
ylwrap

README

		   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.