Go to file
Martin v. Löwis 85c6cbaf2d decl2.c (add_using_namespace): Iterate over namespaces used indirectly.
* decl2.c (add_using_namespace): Iterate over namespaces used
	indirectly.
	* decl.c (lookup_name_real): Accept namespace aliases as locals.
	(cat_namespace_levels): Ignore aliases.
	(duplicate_decls): Ignore duplicate aliases.
	* decl2.c (do_namespace_alias): Process block level namespace
	aliases. Store alias with pushdecl. Remove odr errors.
	* parse.y (namespace_alias): New non-terminal.
	(extdef): Use it.

From-SVN: r21201
1998-07-15 13:27:24 -04:00
config
contrib
etc
gcc decl2.c (add_using_namespace): Iterate over namespaces used indirectly. 1998-07-15 13:27:24 -04:00
include
INSTALL
libf2c Update from Craig, previously missed. 1998-07-15 11:05:36 +00:00
libiberty tweak formatting 1998-07-14 12:16:52 -04:00
libio
libstdc++ Makefile.in (VERSION): Bump to 2.9.0. 1998-07-14 13:06:53 -06:00
texinfo * makeinfo/makeinfo.c (add_word_args): Fix thinko. 1998-07-06 15:58:00 -06:00
xiberty
.cvsignore
ChangeLog
config-ml.in
config.guess
config.sub
configure
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS Add myself as jump.c maintainer. 1998-07-14 14:20:43 -07:00
Makefile.in
missing
mkinstalldirs
move-if-change
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.