Go to file
Mike Frysinger 15d7e0d417 libgloss: finish migration to AM_PROG_AS
When merging iq2000 up a level, it included a partial conversion to
AM_PROG_AS in the common directory.  Finish it for all directories
to kill off the custom LIB_AM_PROG_AS which we no longer need since
we require Automake 1.15 now.
2022-02-24 19:10:39 -05:00
.github/workflows Cygwin: CI: Make sure pdflatex TeX format exists 2022-02-01 16:11:32 +00:00
config Merge autoconf / automake update changes from GCC. 2022-01-17 04:30:37 -05:00
etc etc: switch to automake 2021-11-10 20:14:00 -05:00
include
libgloss libgloss: finish migration to AM_PROG_AS 2022-02-24 19:10:39 -05:00
newlib newlib: fix multilib libg.a parallel builds 2022-02-23 22:01:05 -05:00
texinfo
winsup Cygwin: console: Restore CTRL_BREAK_EVENT handling. 2022-02-24 17:35:21 +09:00
.appveyor.yml Cygwin: Update CI configuration for python version change 2021-12-30 12:52:55 +00:00
.gitattributes
.gitignore Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog
MAINTAINERS
Makefile.def
Makefile.in GCC: Pass --plugin to AR and RANLIB 2022-01-12 08:43:05 -05:00
Makefile.tpl GCC: Pass --plugin to AR and RANLIB 2022-01-12 08:43:05 -05:00
README
README-maintainer-mode Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
ar-lib Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Add support for the haiku operating system. These are the os support patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. All of these architectures are working and most have been stable for quite some time. 2022-01-12 08:43:25 -05:00
configure.ac Add support for the haiku operating system. These are the os support patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. All of these architectures are working and most have been stable for quite some time. 2022-01-12 08:43:25 -05:00
depcomp
djunpack.bat
install-sh
libtool.m4 libtool.m4: fix nm BSD flag detection 2022-01-12 08:49:10 -05:00
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am Merge autoconf / automake update changes from GCC. 2022-01-17 04:30:37 -05:00
setup.com
src-release
symlink-tree
test-driver Bump to autoconf 2.69 and automake 1.15.1 2022-01-12 07:05:02 -05: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.