|
|
|
Some notes on the LAM/MPI Subversion repository:
- Ensure that you have all of the
required software packages before attempting any of these steps.
- Note that no
autoconf- or
automake-generated files are kept in the Subversion
repository. So upon checkout, you will need to generate an executable
configure script. This can be accomplished by running:
./autogen.sh
from the top-level LAM Subversion directory. Note that this may
take several minutes to run, as it will need to traverse the LAM
source tree and invoke itself several times in different directories.
- When you run
autogen.sh, the GNU auto*
tools will be run on several directories. Refer to the requirements
page for the versions of GNU auto* tools that need to be
available on the system. Please note, however, that some bugs in GNU
Automake 1.6 cause autogen.sh to fail. So, if you have
this version of Automake installed, upgrade to version 1.6.3 or
higher.
- When you run the command, you may see a warning about
AC_CONFIG_SUBDIRS -- this is
normal. It is harmless; you can ignore it.
- You'll also get errors and warnings indicating that files such as
install-sh, mkinstalldirs,
missing, and depcomp were installed. The
messages will be similar to the following:
automake: configure.in: installing `./config/install-sh'
automake: configure.in: installing `./config/mkinstalldirs'
automake: configure.in: installing `./config/missing'
automake: configure.in: installing `./config/depcomp'
Don't panic: these are normal. You can
safely ignore these messages.
- Finally, note that whenever any of the following files change,
you will need to run
autogen.sh again (the GNU
auto* tools can be your friends, but they can also
be quite a pain!):
configure.in
acinclude.m4
config/*.m4
|
|
|
