Go to file
Kaveh R. Ghazi 2fde567ece fold-const.c: Include "system.h" to get stdlib.h and stdio.h.
* fold-const.c: Include "system.h" to get stdlib.h and stdio.h.
        (lshift_double): Add parentheses around + or - inside shift.
        (rshift_double): Likewise.
        (size_int_wide): Explicitly set type of `bit_p' to `int'.
        * Makefile.in (fold-const.o): Depend on system.h.

From-SVN: r18057
1998-02-17 15:43:25 -07:00
config Makefile.in (BASE_FLAGS_TO_PASS): Don't pass PICFLAG and PICFLAG_FOR_TARGET. 1998-02-05 17:33:04 -07:00
etc Makefile.in: Add --no-split argument to avoid creating files with names longer than 14... 1997-11-21 20:36:36 -07:00
gcc fold-const.c: Include "system.h" to get stdlib.h and stdio.h. 1998-02-17 15:43:25 -07:00
include
INSTALL Add documentation for OpenServer patch required for static [cd]tors 1998-02-11 23:17:04 +00:00
libf2c Makefile.in ($(lib)): Call $(AR) repeatedly to avoid overflowing argument size limit on ancious System V. 1998-02-10 17:44:50 -07:00
libiberty Makefile.in (FLAGS_TO_PASS): Don't pass PICFLAG. 1998-02-05 17:33:49 -07:00
libio linux.mt (IO_OBJECTS): Add iogetline.o. 1998-02-17 13:54:12 -07:00
libstdc++ Makefile.in (piclist): Check value of enable_shared, not PICFLAG. 1998-02-05 17:34:54 -07:00
texinfo * libtxi/Makefile.in (AR_FLAGS): Defined as "rc". 1998-01-13 13:31:57 -07:00
xiberty
.cvsignore * .cvsignore (*-install): Remove. 1997-09-04 09:49:02 -06:00
ChangeLog Makefile.in (BASE_FLAGS_TO_PASS, [...]): Really add this change to sync Makefile.in with its ChangeLog entries. 1998-02-16 04:20:12 +00:00
config-ml.in config-ml.in (multi-do): LDFLAGS must include multilib designator. 1998-01-13 14:01:03 -07:00
config.guess config.guess: More accurate determination of HP processor types. 1998-01-27 15:15:40 -07:00
config.sub config.guess: More accurate determination of HP processor types. 1998-01-27 15:15:40 -07:00
configure Makefile.in (BASE_FLAGS_TO_PASS): Don't pass PICFLAG and PICFLAG_FOR_TARGET. 1998-02-05 17:33:04 -07:00
configure.in Makefile.in (TARGET_CONFIGDIRS): Add libf2c. 1998-01-31 18:41:24 -07:00
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS Various minor tweaks. 1998-02-17 14:21:20 -07:00
Makefile.in Makefile.in (BASE_FLAGS_TO_PASS, [...]): Really add this change to sync Makefile.in with its ChangeLog entries. 1998-02-16 04:20:13 +00:00
missing
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
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.