Skip to content
Permalink
Browse files

Update the versions of automake and autoconf to

automake (GNU automake) 1.10.1
autoconf (GNU Autoconf) 2.62

While in the area, got rid of some redundant #includes.

There should be no user-visible effects of this change.

Revision created by MOE tool push_codebase.
MOE_MIGRATION=2440
  • Loading branch information...
csilvers+sparsehash
csilvers+sparsehash committed Jun 29, 2011
1 parent 463dc36 commit a5a97ff0d2cb16a2de5405aecf02c868a0073755
Showing with 4,243 additions and 2,999 deletions.
  1. +27 −51 INSTALL
  2. +125 −110 Makefile.in
  3. +102 −84 aclocal.m4
  4. +3 −34 autogen.sh
  5. +0 −99 compile
  6. +52 −59 config.guess
  7. +16 −51 config.sub
  8. +3,453 −2,147 configure
  9. +76 −17 depcomp
  10. +355 −159 install-sh
  11. +34 −27 missing
  12. +0 −158 mkinstalldirs
  13. +0 −3 src/config.h.in
78 INSTALL
@@ -1,41 +1,19 @@
Installation Instructions
*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006, 2007 Free Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Sparsehash-Specific Install Notes
=================================

This code should work on any modern C++ system. It has been tested on
the following systems:
FreeBSD 6.0
FreeBSD 8.1
Linux Fedora Core 3
Linux Fedora Core 4
Linux Fedora Core 5
Linux Fedora Core 6
Linux RedHat 9
Linux Ubuntu 6.06.1
Linux Ubuntu 8
Linux Ubuntu 10 (both 32-bit and 64-bit)
Mac OS X 10.3.9 (Panther)
Mac OS X 10.4.8 (Tiger)
Mac OS X 10.5.8 (Leopard)
Solaris 10 (x86)
Windows XP, Visual Studio 2003 (VC++ 7)
Windows XP, Visual Studio 2005 (VC++ 8)

See README.windows for installation instructions for Windows.


Basic Installation
==================

These are generic installation instructions.
Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
@@ -48,9 +26,9 @@ debugging `configure').

It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
cache files.

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
@@ -60,20 +38,17 @@ some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
`configure' by a program called `autoconf'. You need `configure.ac' if
you want to change it or regenerate `configure' using a newer version
of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
`./configure' to configure the package for your system.

Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.

2. Type `make' to compile the package.

@@ -92,6 +67,9 @@ The simplest way to compile this package is:
all sorts of other programs in order to regenerate files that came
with the distribution.

6. Often, you can also type `make uninstall' to remove the installed
files again.

Compilers and Options
=====================

@@ -103,7 +81,7 @@ details on some of the pertinent environment variables.
by setting variables in the command line or in the environment. Here
is an example:

./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
./configure CC=c99 CFLAGS=-g LIBS=-lposix

*Note Defining Variables::, for more details.

@@ -112,17 +90,15 @@ Compiling For Multiple Architectures

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.

Installation Names
==================
@@ -215,12 +191,12 @@ them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
overridden in the site shell script).

/bin/bash ./configure CONFIG_SHELL=/bin/bash
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug. Until the bug is fixed you can use this workaround:

Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash

`configure' Invocation
======================

0 comments on commit a5a97ff

Please sign in to comment.
You can’t perform that action at this time.