Go to file
Corinna Vinschen 1da77c2678 * fhandler_disk_file.cc (fhandler_base::fstat_by_nfs_ea): Simplify.
Just call nfs_fetch_fattr3 if called via fstat.
	* nfs.cc (nfs_fetch_fattr3): New function to fetch NFS fattr3 info from
	file handle.
	* nfs.h (nfs_fetch_fattr3): Declare.
	* path.cc (symlink_info::check): Simplify NFS case.  Just call
	nfs_fetch_fattr3.
2010-10-02 19:03:44 +00:00
config Sync toplevel and config from GCC. 2010-10-02 14:42:48 +00:00
etc * standards.texi: Import current version from gnustandards 2010-06-08 12:15:36 +00:00
include include/ 2010-09-29 10:14:02 +00:00
libgloss * doc/porting.texi: Fix typos. 2010-09-23 08:07:47 +00:00
newlib 2010-09-21 Craig Howland <howland@LGSInnovations.com> 2010-09-22 03:15:07 +00:00
texinfo
winsup * fhandler_disk_file.cc (fhandler_base::fstat_by_nfs_ea): Simplify. 2010-10-02 19:03:44 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
COPYING.NEWLIB 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
COPYING3
COPYING3.LIB
ChangeLog Allow to pass separate configure arguments for build, host and target. 2010-10-02 14:54:06 +00:00
MAINTAINERS
Makefile.def build: info-gcc, dvi-gcc etc work from unbuilt configured tree. 2010-09-30 21:55:13 +00:00
Makefile.in build: info-gcc, dvi-gcc etc work from unbuilt configured tree. 2010-09-30 21:55:13 +00:00
Makefile.tpl 2010-07-17 Jack Howarth <howarth@bromo.med.uc.edu> 2010-07-18 08:12:40 +00:00
README
README-maintainer-mode Cleanups after the update to Autoconf 2.64, Automake 1.11. 2009-08-22 17:08:06 +00:00
compile
config-ml.in
config.guess /: 2010-06-01 17:53:40 +00:00
config.rpath
config.sub /: 2010-06-01 17:53:40 +00:00
configure Allow to pass separate configure arguments for build, host and target. 2010-10-02 14:54:06 +00:00
configure.ac Allow to pass separate configure arguments for build, host and target. 2010-10-02 14:54:06 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4 Sync Libtool from GCC. 2010-01-09 21:11:32 +00:00
ltgcc.m4
ltmain.sh Sync Libtool from GCC. 2010-01-09 21:11:32 +00:00
ltoptions.m4 Sync Libtool from GCC. 2010-01-09 21:11:32 +00:00
ltsugar.m4
ltversion.m4 Sync Libtool from GCC. 2010-01-09 21:11:32 +00:00
lt~obsolete.m4 Sync Libtool from GCC. 2010-01-09 21:11:32 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com 2009-09-01 Tristan Gingold <gingold@adacore.com> 2009-09-01 13:38:26 +00:00
src-release
symlink-tree
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.