Go to file
Nick Clifton 7592cfd75d PR 6926
* read.c (get_line_sb): Renamed to get_non_macro_line_sb.
        (_find_end_of_line): Add extra parameter indicating if the line is
        inside a macro.  If it is then do not allow the @ character to be
        treated as a line separator character.
        (read_a_source): Update use of _find_end_of_line.
        (find_end_of_line): Likewise.
        (s_irp): Update use of get_line_sb.
        (s_macro): Likewise.
        (do_repeat): Likewise.
        (get_line_sb): New function.  Like the old version of get_line_sb
        except that it takes an extra parameter indicating whether the
        line is inside a macro.
        (get_macro_line_sb): New function.
2008-10-06 08:17:47 +00:00
bfd daily update 2008-10-05 23:00:05 +00:00
binutils binutils/testsuite/ 2008-10-03 15:08:22 +00:00
config
cpu
elfcpp
etc
gas PR 6926 2008-10-06 08:17:47 +00:00
gdb *** empty log message *** 2008-10-06 00:00:33 +00:00
gold * plugin.cc (make_sized_plugin_object): Fix conditional 2008-10-02 18:35:51 +00:00
gprof * configure: Regenerate for new libtool. 2008-09-29 15:36:22 +00:00
include * cris.h (R_CRIS_32_GOT_GD, R_CRIS_16_GOT_GD, R_CRIS_32_GD) 2008-10-04 17:16:30 +00:00
intl
ld PR 6943 2008-10-05 04:12:04 +00:00
libdecnumber
libiberty
opcodes 2008-09-30 H.J. Lu <hongjiu.lu@intel.com> 2008-09-30 19:47:14 +00:00
readline
sim * int.c (trigger_peripheral_interrupt): Clear interrupt pending 2008-10-01 20:44:21 +00:00
texinfo
.cvsignore
ChangeLog * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
lt~obsolete.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
ltgcc.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
ltmain.sh * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
ltoptions.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
ltsugar.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
ltversion.m4 * libtool.m4: Update to libtool 2.2.6. 2008-09-29 15:28:14 +00:00
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.