Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
cfaf553
commit 1dbed0d
Showing
427 changed files
with
51,372 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
IPM was origionally developed and written by David Skinner <deskinner@lbl.gov> | ||
|
||
Since version 0.810 significant coauthorship and contribution has been made by | ||
Nick Wright <njwright@lbl.gov> | ||
Noel Keen <ndkeen@lbl.gov> | ||
Karl Fuerlinger <fuerling@eecs.berkeley.edu> | ||
Sascha Hunold <sascha.hunold@imag.fr> | ||
|
||
suggestions, contributions and collaborations welcome. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
Copyright (c) 2003, The Regents of the University of California, through | ||
Lawrence Berkeley National Laboratory (subject to receipt of any required | ||
approvals from U.S. Dept. of Energy) All rights reserved. | ||
|
||
Redistribution and use in source and binary forms, with or without modification, | ||
are permitted provided that the following conditions are met: | ||
|
||
(1) Redistributions of source code must retain the above copyright notice, this | ||
list of conditions and the following disclaimer. | ||
(2) Redistributions in binary form must reproduce the above copyright notice, | ||
this list of conditions and the following disclaimer in the documentation | ||
and/or other materials provided with the distribution. | ||
(3) Neither the name of Lawrence Berkeley National Laboratory, U.S. Dept. of | ||
Energy nor the names of its contributors may be used to endorse or promote | ||
products derived from this software without specific prior written permission. | ||
|
||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND | ||
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | ||
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE | ||
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR | ||
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES | ||
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; | ||
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON | ||
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | ||
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS | ||
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
/AUTHORS/1.3/Fri Nov 12 19:14:43 2010// | ||
/COPYING/1.1.1.1/Mon May 11 17:58:05 2009// | ||
/ChangeLog/1.1/Fri Mar 26 19:00:00 2010// | ||
/INSTALL/1.2/Fri May 14 17:57:48 2010// | ||
/LICENSE/1.1.1.1/Mon May 11 17:58:05 2009// | ||
/Makefile.am/1.8/Thu Nov 11 02:45:22 2010// | ||
/Makefile.clean-local/1.1/Fri Mar 26 19:00:00 2010// | ||
/Makefile.orig/1.1/Fri Mar 26 19:00:00 2010// | ||
/NEWS/1.1/Fri Mar 26 19:00:00 2010// | ||
/README/1.2/Tue Nov 10 00:56:42 2009// | ||
/TODO/1.7/Wed Nov 10 22:31:43 2010// | ||
/VERSION/1.1/Tue Dec 8 22:42:13 2009// | ||
/configure.ac/1.24/Tue Apr 16 07:22:07 2013// | ||
/make_config/1.31/Fri Dec 23 12:03:12 2011// | ||
D/bin//// | ||
D/doc//// | ||
D/etc//// | ||
D/include//// | ||
D/m4//// | ||
D/src//// | ||
D/test//// | ||
D/utils//// |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
ipm |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
/project/projectdirs/ipm/cvs |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,236 @@ | ||
Installation Instructions | ||
************************* | ||
|
||
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free | ||
Software Foundation, Inc. | ||
|
||
This file is free documentation; the Free Software Foundation gives | ||
unlimited permission to copy, distribute and modify it. | ||
|
||
Basic Installation | ||
================== | ||
|
||
These are generic installation instructions. | ||
|
||
The `configure' shell script attempts to guess correct values for | ||
various system-dependent variables used during compilation. It uses | ||
those values to create a `Makefile' in each directory of the package. | ||
It may also create one or more `.h' files containing system-dependent | ||
definitions. Finally, it creates a shell script `config.status' that | ||
you can run in the future to recreate the current configuration, and a | ||
file `config.log' containing compiler output (useful mainly for | ||
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 | ||
disabled by default to prevent problems with accidental use of stale | ||
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 | ||
diffs or instructions to the address given in the `README' so they can | ||
be considered for the next release. If you are using the cache, and at | ||
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'. | ||
|
||
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. | ||
|
||
Running `configure' takes awhile. While running, it prints some | ||
messages telling which features it is checking for. | ||
|
||
2. Type `make' to compile the package. | ||
|
||
3. Optionally, type `make check' to run any self-tests that come with | ||
the package. | ||
|
||
4. Type `make install' to install the programs and any data files and | ||
documentation. | ||
|
||
5. You can remove the program binaries and object files from the | ||
source code directory by typing `make clean'. To also remove the | ||
files that `configure' created (so you can compile the package for | ||
a different kind of computer), type `make distclean'. There is | ||
also a `make maintainer-clean' target, but that is intended mainly | ||
for the package's developers. If you use it, you may have to get | ||
all sorts of other programs in order to regenerate files that came | ||
with the distribution. | ||
|
||
Compilers and Options | ||
===================== | ||
|
||
Some systems require unusual options for compilation or linking that the | ||
`configure' script does not know about. Run `./configure --help' for | ||
details on some of the pertinent environment variables. | ||
|
||
You can give `configure' initial values for configuration parameters | ||
by setting variables in the command line or in the environment. Here | ||
is an example: | ||
|
||
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix | ||
|
||
*Note Defining Variables::, for more details. | ||
|
||
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 | ||
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. | ||
|
||
Installation Names | ||
================== | ||
|
||
By default, `make install' installs the package's commands under | ||
`/usr/local/bin', include files under `/usr/local/include', etc. You | ||
can specify an installation prefix other than `/usr/local' by giving | ||
`configure' the option `--prefix=PREFIX'. | ||
|
||
You can specify separate installation prefixes for | ||
architecture-specific files and architecture-independent files. If you | ||
pass the option `--exec-prefix=PREFIX' to `configure', the package uses | ||
PREFIX as the prefix for installing programs and libraries. | ||
Documentation and other data files still use the regular prefix. | ||
|
||
In addition, if you use an unusual directory layout you can give | ||
options like `--bindir=DIR' to specify different values for particular | ||
kinds of files. Run `configure --help' for a list of the directories | ||
you can set and what kinds of files go in them. | ||
|
||
If the package supports it, you can cause programs to be installed | ||
with an extra prefix or suffix on their names by giving `configure' the | ||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | ||
|
||
Optional Features | ||
================= | ||
|
||
Some packages pay attention to `--enable-FEATURE' options to | ||
`configure', where FEATURE indicates an optional part of the package. | ||
They may also pay attention to `--with-PACKAGE' options, where PACKAGE | ||
is something like `gnu-as' or `x' (for the X Window System). The | ||
`README' should mention any `--enable-' and `--with-' options that the | ||
package recognizes. | ||
|
||
For packages that use the X Window System, `configure' can usually | ||
find the X include and library files automatically, but if it doesn't, | ||
you can use the `configure' options `--x-includes=DIR' and | ||
`--x-libraries=DIR' to specify their locations. | ||
|
||
Specifying the System Type | ||
========================== | ||
|
||
There may be some features `configure' cannot figure out automatically, | ||
but needs to determine by the type of machine the package will run on. | ||
Usually, assuming the package is built to be run on the _same_ | ||
architectures, `configure' can figure that out, but if it prints a | ||
message saying it cannot guess the machine type, give it the | ||
`--build=TYPE' option. TYPE can either be a short name for the system | ||
type, such as `sun4', or a canonical name which has the form: | ||
|
||
CPU-COMPANY-SYSTEM | ||
|
||
where SYSTEM can have one of these forms: | ||
|
||
OS KERNEL-OS | ||
|
||
See the file `config.sub' for the possible values of each field. If | ||
`config.sub' isn't included in this package, then this package doesn't | ||
need to know the machine type. | ||
|
||
If you are _building_ compiler tools for cross-compiling, you should | ||
use the option `--target=TYPE' to select the type of system they will | ||
produce code for. | ||
|
||
If you want to _use_ a cross compiler, that generates code for a | ||
platform different from the build platform, you should specify the | ||
"host" platform (i.e., that on which the generated programs will | ||
eventually be run) with `--host=TYPE'. | ||
|
||
Sharing Defaults | ||
================ | ||
|
||
If you want to set default values for `configure' scripts to share, you | ||
can create a site shell script called `config.site' that gives default | ||
values for variables like `CC', `cache_file', and `prefix'. | ||
`configure' looks for `PREFIX/share/config.site' if it exists, then | ||
`PREFIX/etc/config.site' if it exists. Or, you can set the | ||
`CONFIG_SITE' environment variable to the location of the site script. | ||
A warning: not all `configure' scripts look for a site script. | ||
|
||
Defining Variables | ||
================== | ||
|
||
Variables not defined in a site shell script can be set in the | ||
environment passed to `configure'. However, some packages may run | ||
configure again during the build, and the customized values of these | ||
variables may be lost. In order to avoid this problem, you should set | ||
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: | ||
|
||
/bin/bash ./configure CONFIG_SHELL=/bin/bash | ||
|
||
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent | ||
configuration-related scripts to be executed by `/bin/bash'. | ||
|
||
`configure' Invocation | ||
====================== | ||
|
||
`configure' recognizes the following options to control how it operates. | ||
|
||
`--help' | ||
`-h' | ||
Print a summary of the options to `configure', and exit. | ||
|
||
`--version' | ||
`-V' | ||
Print the version of Autoconf used to generate the `configure' | ||
script, and exit. | ||
|
||
`--cache-file=FILE' | ||
Enable the cache: use and save the results of the tests in FILE, | ||
traditionally `config.cache'. FILE defaults to `/dev/null' to | ||
disable caching. | ||
|
||
`--config-cache' | ||
`-C' | ||
Alias for `--cache-file=config.cache'. | ||
|
||
`--quiet' | ||
`--silent' | ||
`-q' | ||
Do not print messages saying which checks are being made. To | ||
suppress all normal output, redirect it to `/dev/null' (any error | ||
messages will still be shown). | ||
|
||
`--srcdir=DIR' | ||
Look for the package's source code in directory DIR. Usually | ||
`configure' can determine that directory automatically. | ||
|
||
`configure' also accepts some other, not widely useful, options. Run | ||
`configure --help' for more details. | ||
|
Oops, something went wrong.