From 38178e3b480cbe8487df8ad3083c0938db5be7ac Mon Sep 17 00:00:00 2001 From: simonpj Date: Thu, 5 Feb 2004 09:46:22 +0000 Subject: [PATCH] [project @ 2004-02-05 09:46:22 by simonpj] Mention autoreconf, not autoconf --- docs/building/building.sgml | 48 +++++++++++++++++++++++++------------------ 1 file changed, 28 insertions(+), 20 deletions(-) diff --git a/docs/building/building.sgml b/docs/building/building.sgml index cc68719..7196bf1 100644 --- a/docs/building/building.sgml +++ b/docs/building/building.sgml @@ -1298,22 +1298,22 @@ $ cvs checkout nofib/spectral - Autoconf - pre-supposed: Autoconf - Autoconf, pre-supposed + Autoreconf + pre-supposed: Autoreconf + Autoreconf, pre-supposed - GNU Autoconf is needed if you intend to build from the + GNU Autoreconf is needed if you intend to build from the CVS sources, it is not needed if you just intend to build a standard source distribution. - Version 2.52 or later of autoconf is required. + Version 2.52 or later of autoreconf is required. NB. vesrion 2.13 will no longer work, as of GHC version 6.1. - Autoconf builds the configure + Autoreconf builds the configure script from configure.ac and aclocal.m4. If you modify either of - these files, you'll need autoconf to + these files, you'll need autoreconf to rebuild configure. @@ -1434,7 +1434,8 @@ $ cvs checkout nofib/spectral want a completely standard build, then the following should work: -$ ./configure +$ autoreconf +$ ./configure $ make $ make install @@ -1606,20 +1607,27 @@ $ make install Change directory to $(FPTOOLS_TOP) and issue the command - autoconfautoconf + +autoreconf + + autoreconf (with no arguments). This GNU program converts $(FPTOOLS_TOP)/configure.ac to a shell script called $(FPTOOLS_TOP)/configure. + If autoreconf bleats that it can't write the file configure, + then delete the latter and try again. Note that you must use autoreconf, + and not the old autoconf! If you erroneously use the latter, you'll get + a message like "No rule to make target 'mk/config.h.in'". Some projects, including GHC, have their own configure script. If there's an $(FPTOOLS_TOP)/<project>/configure.ac, - then you need to run autoconf in that + then you need to run autoreconf in that directory too. - Both these steps are completely + These steps are completely platform-independent; they just mean that the human-written file (configure.ac) can be short, although the resulting shell script, @@ -1899,7 +1907,7 @@ $ cd /scratch/joe-bloggs/myfptools-sun4 Prepare for system configuration: -$ autoconf +$ autoreconf (You can skip this step if you are starting from a @@ -1908,11 +1916,11 @@ $ autoconf mk/config.h.in.) Some projects, including GHC itself, have their own - configure scripts, so it is necessary to run autoconf again + configure scripts, so it is necessary to run autoreconf again in the appropriate subdirectories. eg: -$ (cd ghc; autoconf) +$ (cd ghc; autoreconf) @@ -4454,7 +4462,7 @@ During the installation dialogue, make sure that you select all of the following openssh, - autoconf, + autoreconf, automake, @@ -4717,7 +4725,7 @@ you about Windows-specific wrinkles. -Run autoconf both in fptools +Run autoreconf both in fptools and in fptools/ghc. If you omit the latter step you'll get an error when you run ./configure: @@ -4732,11 +4740,11 @@ configure: error: ./configure failed for ghc - autoconf seems to create the file configure -read-only. So if you need to run autoconf again (which I sometimes do for safety's sake), + autoreconf seems to create the file configure +read-only. So if you need to run autoreconf again (which I sometimes do for safety's sake), you get -/usr/bin/autoconf: cannot create configure: permission denied +/usr/bin/autoreconf: cannot create configure: permission denied Solution: delete configure first. @@ -4759,7 +4767,7 @@ can be really confusing. - After autoconf run ./configure in + After autoreconf run ./configure in fptools/ thus: -- 1.7.10.4