2
0
mirror of git://gcc.gnu.org/git/gcc.git synced 2025-04-27 19:01:11 +08:00
Kaveh R. Ghazi a81fb89ebe aclocal.m4 (GCC_NEED_DECLARATION): Modify macro to accept a shell variable argument instead of only hard coded...
* aclocal.m4 (GCC_NEED_DECLARATION): Modify macro to accept a
        shell variable argument instead of only hard coded functions.
        (GCC_NEED_DECLARATIONS): New macro to accept multiple functions.
        * configure.in: Collapse multiple calls to AC_CHECK_FUNCS into one
        call.  Collapse multiple calls to GCC_NEED_DECLARATION into one
        call to GCC_NEED_DECLARATIONS (new macro.)  Check if we need
        declarations for bcopy, bcmp and bzero.
        * acconfig.h: Add stubs for bcopy, bcmp and bzero declarations.
        * gansidecl.h: If we have bcopy but don't declare it, then do so.
        Likewise for bcmp and bzero.  Only define macros for bcopy, bcmp,
        bzero, index and rindex if they aren't already present.

From-SVN: r17563
1998-01-31 17:48:06 -07:00
1998-01-03 17:10:33 -07:00
1997-12-09 12:20:43 -07:00
1998-01-17 14:30:39 -07:00
1998-01-28 02:48:01 -07:00
1998-01-26 09:15:46 -07:00

		   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.
Description
No description provided
Readme 2.1 GiB
Languages
C++ 31.9%
C 31.3%
Ada 12%
D 6.5%
Go 6.4%
Other 11.5%