[project @ 1999-12-07 14:46:31 by chak]

Package local configuration scripts allow to modularise the configuration (we
start by having one for ghc):
* Modularised configuration avoids unnecessary dependencies for individual
  packages.
* Furthermore, package local configuration (such as entering version
  information into rpm .spec files) is possible.

configure.in

@@ -16,6 +16,12 @@ dnl
 # First off, a distrib sanity check..
 AC_INIT(mk/config.mk.in)
 
+dnl * Declare subdirectories that have a private configure script
+dnl
+dnl After the toplevel configuration is complete, the script will recurse into
+dnl these subdirectories (the use of cache values makes repeated checks cheap)
+AC_CONFIG_SUBDIRS(ghc)
+
 # -------------------------------------------------------------------------
 # Prepare to generate the following header files
 #

ghc/configure.in

+dnl GHC-only part of fptools configuration
+dnl 
+dnl Copyright (c) 1999 Manuel M. T. Chakravarty <chak@acm.org>
+dnl 
+dnl This file is subject to the same free software license as GHC.
+
+dnl ######################################################################
+dnl Process this file with autoconf to produce a configure script.
+dnl ######################################################################
+
+
+dnl * Initialise and check sanity.
+AC_INIT(ghc.spec.in)
+
+dnl * Compute the version number.
+version=`sed -e 's/.*\([[0-9]]\)\.\([[0-9]]*\).*/\1.\2/' VERSION`
+patchlevel=1
+
+dnl These are needed by the .spec file.
+AC_SUBST(version)
+AC_SUBST(patchlevel)
+
+dnl * Write the results...
+AC_OUTPUT(ghc.spec)