Commit 732e3250 authored by Bruno Coudoin's avatar Bruno Coudoin

Updated our build system to support automake1.10

	You still need to copy config.rpath from the gettext
	package manualy.
	Merged from trunk r3296


svn path=/branches/gcomprixogoo/; revision=3297
parent 1c200892
This diff is collapsed.
2007-10-03 Bruno coudoin <bruno.coudoin@free.fr>
2008-03-12 Bruno coudoin <bruno.coudoin@free.fr>
Updated our build system to support automake1.10
You still need to copy config.rpath from the gettext
package manualy.
Merged from trunk r3296
* ABOUT-NLS:
* INSTALL:
* configure.in:
* docs/C/Makefile.am:
* docs/C/texinfo.tex:
* docs/eu/Makefile.am:
* docs/fr/Makefile.am:
* gnome2-macros/gnome-autogen.sh:
* install-sh:
* list_translators.sh:
2008-03-01 Bruno coudoin <bruno.coudoin@free.fr>
Made the chess activity to search for gnuchess in usual
directory if it is not found in the one detected at compilation
......
GCompris Specific Instructions
==============================
Gcompris can be installed anywhere on your hard drive.
for example, you can use:
sh configure --prefix=/home/bruno/gcompris
make
make install
Warning: You cannot use ~ in the prefix, it must be a full path.
Warning: It has been reported that make -j 2 (or more) break the compilation
This will install GCompris and all its data files under
/home/bruno/gcompris
Then, run /home/bruno/gcompris/bin/gcompris
Gcompris requires gtk-libs, libxml2, gnomecanvas, sqlite, and gdk-pixbuf.
gcompris also requires the gnuchess and gnucap package for the chess activity and
electricity to run. If you have gnome-gnuchess instead of gnuchess, autoconf will
detect it and compile with it.
GCompris includes several activity written in python.
To enable them, you need to have python installed on your system with the following packages:
libpython
python
libpython2.4-devel
python-base
python-sqlite2 (if it's not packaged, download and install it from http://initd.org/tracker/pysqlite)
For the sound managed internally, you also need gstreamer:
libgstreamer0.10-0 libgstreamer0.10-dev
On Mandriva, you will need to install their -devel counterpart package in
order to be abble to compile it plus intltool, tetex.
In order to compile GCompris on a mandriva 2007 you must install :
urpmi pkgconfig
urpmi autoconf2.5
urpmi glib-gettext
urpmi gettext-devel
urpmi intltool
urpmi automake1.7
urpmi libglib2.0_0-devel
urpmi libgdk_pixbuf2.0_0-devel
urpmi libgnomeui2_0-devel
urpmi libgstreamer libgstreamer-devel (Unchecked)
urpmi python-gtk-devel
urpmi libpython2.4-devel
urpmi pygtk2.0-devel
urpmi texinfo
urpmi texi2html
urpmi tetex
urpmi gnuchess
urpmi gnucap
urpmi libtool
urpmi libsqlite3_0 libsqlite3_0-devel
urpmi python-sqlite2
urpmi libxxf86vm1-devel
WARNING
=======
We are using sqlite but it doesn't work on NFS mounted partitions.
If you home directory is on a remote server, then use run GCompris
with a local file for its database like:
gcompris --database=/tmp/gcompris.db
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006 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.
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
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, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
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 at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
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.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The file `configure.ac' (or `configure.in') is used to create
`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.
......@@ -124,49 +70,49 @@ The simplest way to compile this package is:
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
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:
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
./configure CC=c99 CFLAGS=-g 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
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 supports 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
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
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
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
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=PATH' to specify different values for particular
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.
......@@ -177,7 +123,7 @@ option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
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
......@@ -192,48 +138,86 @@ you can use the `configure' options `--x-includes=DIR' and
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
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
See the file `config.sub' for the possible values of each field. If
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 host type.
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 are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
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'.
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.
Operation Controls
Defining Variables
==================
`configure' recognizes the following options to control how it
operates.
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:
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
./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).
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/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'
......@@ -245,8 +229,6 @@ operates.
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
`configure' also accepts some other, not widely useful, options.
GCompris / I Have Understood
GCompris is a GNU package
GCompris / I Got IT
GCompris is a GNU package
GCompris is an educational game for children starting at 3.
It uses GTK and the GNOME Libraries (especially the GNOME canvas),
the libxml and gtk-pixbuf.
It uses GTK the GOO canvas, libxml2 and librsvg.
Read the file 'README.installation' to get specific information on how
to build GCompris.
-------------------------------------------------------------------------------
GCompris MOTIVATION
......@@ -47,3 +48,4 @@ About You:
Read the README.translators to get additional information on GCompris
translation.
GCompris Specific Instructions
==============================
Gcompris can be installed anywhere on your hard drive.
for example, you can use:
sh configure --prefix=/home/bruno/gcompris
make
make install
Warning: You cannot use ~ in the prefix, it must be a full path.
Warning: It has been reported that make -j 2 (or more) break the compilation
This will install GCompris and all its data files under
/home/bruno/gcompris
Then, run /home/bruno/gcompris/bin/gcompris
Gcompris requires gtk-libs, libxml2, gnomecanvas, sqlite, and gdk-pixbuf.
gcompris also requires the gnuchess and gnucap package for the chess activity and
electricity to run. If you have gnome-gnuchess instead of gnuchess, autoconf will
detect it and compile with it.
GCompris includes several activity written in python.
To enable them, you need to have python installed on your system with the following packages:
libpython
python
libpython2.4-devel
python-base
python-sqlite2 (if it's not packaged, download and install it from http://initd.org/tracker/pysqlite)
For the sound managed internally, you also need gstreamer:
libgstreamer0.10-0 libgstreamer0.10-dev
On Mandriva, you will need to install their -devel counterpart package in
order to be abble to compile it plus intltool, tetex.
In order to compile GCompris on a mandriva 2007 you must install :
urpmi pkgconfig
urpmi autoconf2.5
urpmi glib-gettext
urpmi gettext-devel
urpmi intltool
urpmi automake1.7
urpmi libglib2.0_0-devel
urpmi libgdk_pixbuf2.0_0-devel
urpmi libgnomeui2_0-devel
urpmi libgstreamer libgstreamer-devel (Unchecked)
urpmi python-gtk-devel
urpmi libpython2.4-devel
urpmi pygtk2.0-devel
urpmi texinfo
urpmi texi2html
urpmi tetex
urpmi gnuchess
urpmi gnucap
urpmi libtool
urpmi libsqlite3_0 libsqlite3_0-devel
urpmi python-sqlite2
urpmi libxxf86vm1-devel
WARNING
=======
We are using sqlite but it doesn't work on NFS mounted partitions.
If you home directory is on a remote server, then use run GCompris
with a local file for its database like:
gcompris --database=/tmp/gcompris.db
......@@ -44,6 +44,7 @@ AC_HEADER_DIRENT
AC_PROG_CC
AM_PROG_CC_STDC
AM_PROG_CC_C_O
AC_HEADER_STDC
AC_PROG_INTLTOOL
......
......@@ -23,19 +23,19 @@ info_TEXINFOS = gcompris.texi
# $(INSTALL_DATA) $(srcdir)/overview.jpg $(DESTDIR)$(gcompris_helpdir)
# $(INSTALL_DATA) $(srcdir)/topic.dat $(DESTDIR)$(gcompris_helpdir)
%.html: %.texi
gcompris.html: gcompris.texi
texi2html -monolithic $<
%.eps: %.dia
overview.eps: overview.dia
dia $< -e $@
%.ps: %.dvi
gcompris.ps: gcompris.dvi
dvips -o $@ $<
%.dvi: %.texi
gcompris.dvi: gcompris.texi
texi2dvi $<
%.pdf: %.ps
gcompris.pdf: gcompris.ps
ps2pdf $<
gcompris.pdf gcompris.dvi: overview.eps
......
This diff is collapsed.
......@@ -21,21 +21,22 @@ install-data-local:
$(INSTALL_DATA) $(srcdir)/overview.jpg $(DESTDIR)$(gcompris_helpdir)
$(INSTALL_DATA) $(srcdir)/topic.dat $(DESTDIR)$(gcompris_helpdir)
%.html: %.texi
gcompris.html: gcompris.texi
texi2html -monolithic $<
%.eps: %.dia
overview.eps: overview.dia
dia $< -e $@
%.ps: %.dvi
gcompris.ps: gcompris.dvi
dvips -o $@ $<
%.dvi: %.texi
gcompris.dvi: gcompris.texi
texi2dvi $<
%.pdf: %.ps
gcompris.pdf: gcompris.ps
ps2pdf $<
gcompris.pdf gcompris.dvi: overview.eps
clean-local:
......
......@@ -22,21 +22,22 @@ all: $(doc)
# $(INSTALL_DATA) $(srcdir)/overview.jpg $(DESTDIR)$(gcompris_helpdir)
# $(INSTALL_DATA) $(srcdir)/topic.dat $(DESTDIR)$(gcompris_helpdir)
%.html: %.texi
gcompris.html: gcompris.texi
texi2html -monolithic $<
%.eps: %.dia
overview.eps: overview.dia
dia $< -e $@
%.ps: %.dvi
gcompris.ps: gcompris.dvi
dvips -o $@ $<
%.dvi: %.texi
gcompris.dvi: gcompris.texi
texi2dvi $<
%.pdf: %.ps
gcompris.pdf: gcompris.ps
ps2pdf $<
gcompris.pdf gcompris.dvi: overview.eps
clean-local:
......
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
echo "Gcompris modified gnome-autogen.sh"
#name of package
PKG_NAME=${PKG_NAME:-Package}
srcdir=${srcdir:-.}
GNOME_COMMON_DATADIR="$BUILD_PATH"
GNOME_COMMON_MACROS_DIR="$BUILD_PATH/gnome2-macros"
# default version requirements ...
REQUIRED_AUTOCONF_VERSION=${REQUIRED_AUTOCONF_VERSION:-2.53}
REQUIRED_AUTOMAKE_VERSION=${REQUIRED_AUTOMAKE_VERSION:-1.9}
REQUIRED_LIBTOOL_VERSION=${REQUIRED_LIBTOOL_VERSION:-1.5}
REQUIRED_GETTEXT_VERSION=${REQUIRED_GETTEXT_VERSION:-0.12}
REQUIRED_GLIB_GETTEXT_VERSION=${REQUIRED_GLIB_GETTEXT_VERSION:-2.2.0}
REQUIRED_INTLTOOL_VERSION=${REQUIRED_INTLTOOL_VERSION:-0.30}
REQUIRED_PKG_CONFIG_VERSION=${REQUIRED_PKG_CONFIG_VERSION:-0.14.0}
REQUIRED_GTK_DOC_VERSION=${REQUIRED_GTK_DOC_VERSION:-1.0}
REQUIRED_DOC_COMMON_VERSION=${REQUIRED_DOC_COMMON_VERSION:-2.3.0}
REQUIRED_GNOME_DOC_UTILS_VERSION=${REQUIRED_GNOME_DOC_UTILS_VERSION:-0.4.2}
export GNOME_COMMON_DATADIR
export GNOME_COMMON_MACROS_DIR
# a list of required m4 macros. Package can set an initial value
REQUIRED_M4MACROS=${REQUIRED_M4MACROS:-}
FORBIDDEN_M4MACROS=${FORBIDDEN_M4MACROS:-}
ACLOCAL_FLAGS="-I $GNOME_COMMON_MACROS_DIR $ACLOCAL_FLAGS"
export ACLOCAL_FLAGS
# Not all echo versions allow -n, so we check what is possible. This test is
# based on the one in autoconf.
ECHO_C=
ECHO_N=
case `echo -n x` in
-n*)
case `echo 'x\c'` in
*c*) ;;
*) ECHO_C='\c';;
esac;;
*)
ECHO_N='-n';;
esac
. $GNOME_COMMON_MACROS_DIR/autogen.sh
# some terminal codes ...
boldface="`tput bold 2>/dev/null`"
normal="`tput sgr0 2>/dev/null`"
printbold() {
echo $ECHO_N "$boldface" $ECHO_C
echo "$@"
echo $ECHO_N "$normal" $ECHO_C
}
printerr() {
echo "$@" >&2
}
# Usage:
# compare_versions MIN_VERSION ACTUAL_VERSION
# returns true if ACTUAL_VERSION >= MIN_VERSION
compare_versions() {
ch_min_version=$1
ch_actual_version=$2
ch_status=0
IFS="${IFS= }"; ch_save_IFS="$IFS"; IFS="."
set $ch_actual_version
for ch_min in $ch_min_version; do
ch_cur=`echo $1 | sed 's/[^0-9].*$//'`; shift # remove letter suffixes
if [ -z "$ch_min" ]; then break; fi
if [ -z "$ch_cur" ]; then ch_status=1; break; fi
if [ $ch_cur -gt $ch_min ]; then break; fi
if [ $ch_cur -lt $ch_min ]; then ch_status=1; break; fi
done
IFS="$ch_save_IFS"
return $ch_status
}
# Usage:
# version_check PACKAGE VARIABLE CHECKPROGS MIN_VERSION SOURCE
# checks to see if the package is available
version_check() {
vc_package=$1
vc_variable=$2
vc_checkprogs=$3
vc_min_version=$4
vc_source=$5
vc_status=1
vc_checkprog=`eval echo "\\$$vc_variable"`
if [ -n "$vc_checkprog" ]; then
printbold "using $vc_checkprog for $vc_package"
return 0
fi
if test "x$vc_package" = "xautomake" -a "x$vc_min_version" = "x1.4"; then
vc_comparator="="
else
vc_comparator=">="
fi
printbold "checking for $vc_package $vc_comparator $vc_min_version..."
for vc_checkprog in $vc_checkprogs; do
echo $ECHO_N " testing $vc_checkprog... " $ECHO_C
if $vc_checkprog --version < /dev/null > /dev/null 2>&1; then
vc_actual_version=`$vc_checkprog --version | head -n 1 | \
sed 's/^.*[ ]\([0-9.]*[a-z]*\).*$/\1/'`
if compare_versions $vc_min_version $vc_actual_version; then
echo "found $vc_actual_version"
# set variables
eval "$vc_variable=$vc_checkprog; \
${vc_variable}_VERSION=$vc_actual_version"
vc_status=0
break
else
echo "too old (found version $vc_actual_version)"
fi
else
echo "not found."
fi
done
if [ "$vc_status" != 0 ]; then
printerr "***Error***: You must have $vc_package $vc_comparator $vc_min_version installed"
printerr " to build $PKG_NAME. Download the appropriate package for"
printerr " from your distribution or get the source tarball at"
printerr " $vc_source"
printerr
fi
return $vc_status
}
# Usage:
# require_m4macro filename.m4
# adds filename.m4 to the list of required macros
require_m4macro() {
case "$REQUIRED_M4MACROS" in
$1\ * | *\ $1\ * | *\ $1) ;;
*) REQUIRED_M4MACROS="$REQUIRED_M4MACROS $1" ;;
esac
}
forbid_m4macro() {
case "$FORBIDDEN_M4MACROS" in
$1\ * | *\ $1\ * | *\ $1) ;;
*) FORBIDDEN_M4MACROS="$FORBIDDEN_M4MACROS $1" ;;
esac
}
# Usage:
# add_to_cm_macrodirs dirname
# Adds the dir to $cm_macrodirs, if it's not there yet.
add_to_cm_macrodirs() {
case $cm_macrodirs in
"$1 "* | *" $1 "* | *" $1") ;;
*) cm_macrodirs="$cm_macrodirs $1";;
esac
}
# Usage:
# print_m4macros_error
# Prints an error message saying that autoconf macros were misused
print_m4macros_error() {
printerr "***Error***: some autoconf macros required to build $PKG_NAME"
printerr " were not found in your aclocal path, or some forbidden"
printerr " macros were found. Perhaps you need to adjust your"
printerr " ACLOCAL_FLAGS?"
printerr
}
# Usage:
# check_m4macros
# Checks that all the requested macro files are in the aclocal macro path
# Uses REQUIRED_M4MACROS and ACLOCAL variables.
check_m4macros() {
# construct list of macro directories
cm_macrodirs=`$ACLOCAL --print-ac-dir`
# aclocal also searches a version specific dir, eg. /usr/share/aclocal-1.9
# but it contains only Automake's own macros, so we can ignore it.
# Read the dirlist file, supported by Automake >= 1.7.
if compare_versions 1.7 $AUTOMAKE_VERSION && [ -s $cm_macrodirs/dirlist ]; then
cm_dirlist=`sed 's/[ ]*#.*//;/^$/d' $cm_macrodirs/dirlist`
if [ -n "$cm_dirlist" ] ; then
for cm_dir in $cm_dirlist; do
if [ -d $cm_dir ]; then
add_to_cm_macrodirs $cm_dir
fi
done
fi
fi
# Parse $ACLOCAL_FLAGS
set - $ACLOCAL_FLAGS
while [