Red Hat's newlib C library with support for Jehanne
Go to file
Christopher Faylor 243a041bd0 * dll_init.h (class dll_list): Reorder functions to avoid compiler "can't
inline" warnings.
* security.h (class cygsid): Ditto.
* sigproc.cc (get_proc_lock): Ditto.
* sigproc.h (class sigframe): Ditto.
* sync.h (class muto): Ditto.
* fhandler.h (fhandler_base::get_guard): Actually MAKE virtual as previously
indicated.
* pipe.cc (make_pipe): Remove extraneous set_errno.
* syscalls.cc (_open): Ditto.
* select.cc (peek_pipe): Need to check that there is still something to read
from the pipe after acquiring the mutex since another process/thread could have
eaten the input before we got to acquiring the lock.  (Thanks to Nick Duffek
for this inspiration.)
2001-11-03 03:32:27 +00:00
config
etc
include Add MMIX support 2001-10-30 15:20:10 +00:00
libgloss 2001-10-31 Jeff Johnston <jjohnstn@redhat.com> 2001-10-31 19:26:13 +00:00
newlib 2001-11-01 Arati Dikey <aratidikey@hotmail.com> 2001-11-01 19:47:32 +00:00
texinfo
winsup * dll_init.h (class dll_list): Reorder functions to avoid compiler "can't 2001-11-03 03:32:27 +00:00
ChangeLog 2001-10-24 Jeff Holcomb <jeffh@redhat.com> 2001-10-24 20:02:25 +00:00
config-ml.in
config.guess * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
config.if
config.sub * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
configure
configure.in 2001-09-19 Ben Elliston <bje@redhat.com> 2001-09-19 06:07:36 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB
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
ltcf-c.sh * ltcf-c.sh (archive_cmds, archive_expsym_cmds) [solaris, 2001-06-04 19:33:12 +00:00
ltcf-cxx.sh * ltcf-cxx.sh (osf3/osf4/osf5): Support creation of C++ shared 2001-05-28 21:05:35 +00:00
ltcf-gcj.sh
ltconfig * ltconfig, ltmain.sh: Upgrade to libtool 1.4a 1.641.2.256. 2001-05-28 20:56:20 +00:00
ltmain.sh * ltconfig, ltmain.sh: Upgrade to libtool 1.4a 1.641.2.256. 2001-05-28 20:56:20 +00:00
MAINTAINERS * MAINTAINERS: Clarify libiberty merge rules and procedures. 2001-07-26 14:20:05 +00:00
Makefile.in 2001-10-24 Jeff Holcomb <jeffh@redhat.com> 2001-10-24 20:02:25 +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.