Menu
▾
▴
autotoolset-commits — Commit mails
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(13) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <mro...@us...> - 2007-05-16 03:26:44
|
Revision: 49
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=49&view=rev
Author: mroberto
Date: 2007-05-15 20:26:45 -0700 (Tue, 15 May 2007)
Log Message:
-----------
Updating the tutorial.
Modified Paths:
--------------
htdocs/tutorial.html
Modified: htdocs/tutorial.html
===================================================================
--- htdocs/tutorial.html 2007-05-16 03:24:24 UTC (rev 48)
+++ htdocs/tutorial.html 2007-05-16 03:26:45 UTC (rev 49)
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
-<!-- Created on May, 14 2007 by texi2html 1.76 -->
+<!-- Created on May, 16 2007 by texi2html 1.76 -->
<!--
Written by: Lionel Cons <Lio...@ce...> (original author)
Karl Berry <ka...@fr...>
@@ -18,7 +18,7 @@
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.76">
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
@@ -14097,7 +14097,7 @@
</tr></table>
<h1>About This Document</h1>
<p>
- This document was generated by <em>Marcelo Roberto Jimenez</em> on <em>May, 14 2007</em> using <a href="http://texi2html.cvshome.org/"><em>texi2html 1.76</em></a>.
+ This document was generated by <em>Marcelo Roberto Jimenez</em> on <em>May, 16 2007</em> using <a href="http://texi2html.cvshome.org/"><em>texi2html 1.76</em></a>.
</p>
<p>
The buttons in the navigation panels have the following meaning:
@@ -14199,7 +14199,7 @@
<hr size="1">
<p>
<font size="-1">
- This document was generated by <em>Marcelo Roberto Jimenez</em> on <em>May, 14 2007</em> using <a href="http://texi2html.cvshome.org/"><em>texi2html 1.76</em></a>.
+ This document was generated by <em>Marcelo Roberto Jimenez</em> on <em>May, 16 2007</em> using <a href="http://texi2html.cvshome.org/"><em>texi2html 1.76</em></a>.
</font>
<br>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-16 03:24:22
|
Revision: 48
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=48&view=rev
Author: mroberto
Date: 2007-05-15 20:24:24 -0700 (Tue, 15 May 2007)
Log Message:
-----------
Should probably take out these files from version control.
Modified Paths:
--------------
trunk/misc/makerpm
Modified: trunk/misc/makerpm
===================================================================
--- trunk/misc/makerpm 2007-05-16 02:58:53 UTC (rev 47)
+++ trunk/misc/makerpm 2007-05-16 03:24:24 UTC (rev 48)
@@ -1,4 +1,4 @@
#! /bin/sh
-VERSION=0.11.5
+VERSION=0.11.6
PREFIX=/usr/local
-rpmbuild --sign -ta autotoolset-0.11.5.tar.bz2
+rpmbuild --sign -ta autotoolset-0.11.6.tar.bz2
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-16 02:58:51
|
Revision: 47
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=47&view=rev
Author: mroberto
Date: 2007-05-15 19:58:53 -0700 (Tue, 15 May 2007)
Log Message:
-----------
"ACLOCAL_AMFLAGS= -I m4" is needed in Makefile.am to use autoreconf.
Modified Paths:
--------------
trunk/INSTALL
trunk/Makefile.am
trunk/configure.ac
trunk/doc/tutorial/version.texi
Modified: trunk/INSTALL
===================================================================
--- trunk/INSTALL 2007-05-14 17:07:18 UTC (rev 46)
+++ trunk/INSTALL 2007-05-16 02:58:53 UTC (rev 47)
@@ -102,16 +102,16 @@
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=PREFIX'.
+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=PREFIX', the package will
-use PREFIX 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=DIR' to specify different values for particular
@@ -159,7 +159,7 @@
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
+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
Modified: trunk/Makefile.am
===================================================================
--- trunk/Makefile.am 2007-05-14 17:07:18 UTC (rev 46)
+++ trunk/Makefile.am 2007-05-16 02:58:53 UTC (rev 47)
@@ -19,6 +19,8 @@
EXTRA_DIST = debian reconf
+ACLOCAL_AMFLAGS= -I m4
+
# That would be nice, but this target does not exist :-(
#dist-local:
# rm -f @PACKAGE_TARNAME@-@PACKAGE_VERSION@.tar.gz
Modified: trunk/configure.ac
===================================================================
--- trunk/configure.ac 2007-05-14 17:07:18 UTC (rev 46)
+++ trunk/configure.ac 2007-05-16 02:58:53 UTC (rev 47)
@@ -19,8 +19,11 @@
AC_INIT([GNU autotoolset], [0.11.6],
[Marcelo Roberto Jimenez <mro...@ce...>],
[autotoolset])
+
+AC_CONFIG_AUX_DIR(config.aux)
+AC_CONFIG_MACRO_DIR(m4)
AC_CONFIG_SRCDIR(src/Makefile.am)
-AC_CONFIG_AUX_DIR(config.aux)
+
AM_INIT_AUTOMAKE([dist-bzip2])
# C compiler stuff
Modified: trunk/doc/tutorial/version.texi
===================================================================
--- trunk/doc/tutorial/version.texi 2007-05-14 17:07:18 UTC (rev 46)
+++ trunk/doc/tutorial/version.texi 2007-05-16 02:58:53 UTC (rev 47)
@@ -1,4 +1,4 @@
-@set UPDATED 14 May 2007
+@set UPDATED 15 May 2007
@set UPDATED-MONTH May 2007
@set EDITION 0.11.6
@set VERSION 0.11.6
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-14 17:07:33
|
Revision: 46
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=46&view=rev
Author: mroberto
Date: 2007-05-14 10:07:18 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Update of home page tutorial.
Modified Paths:
--------------
htdocs/tutorial.html
Modified: htdocs/tutorial.html
===================================================================
--- htdocs/tutorial.html 2007-05-14 16:59:41 UTC (rev 45)
+++ htdocs/tutorial.html 2007-05-14 17:07:18 UTC (rev 46)
@@ -1,309 +1,362 @@
-<HTML>
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!-- Created on January, 10 2005 by texi2html 1.64 -->
-<!--
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
+<html>
+<!-- Created on May, 14 2007 by texi2html 1.76 -->
+<!--
Written by: Lionel Cons <Lio...@ce...> (original author)
Karl Berry <ka...@fr...>
Olaf Bachmann <oba...@ma...>
and many others.
-Maintained by: Olaf Bachmann <oba...@ma...>
-Send bugs and suggestions to <tex...@ma...>
-
+Maintained by: Many creative people <de...@te...>
+Send bugs and suggestions to <us...@te...>
+
-->
-<HEAD>
-<TITLE>Learning the GNU development tools: </TITLE>
+<head>
+<title>Learning the GNU development tools: Preface</title>
-<META NAME="description" CONTENT="Learning the GNU development tools: ">
-<META NAME="keywords" CONTENT="Learning the GNU development tools: ">
-<META NAME="resource-type" CONTENT="document">
-<META NAME="distribution" CONTENT="global">
-<META NAME="Generator" CONTENT="texi2html 1.64">
+<meta name="description" content="Learning the GNU development tools: Preface">
+<meta name="keywords" content="Learning the GNU development tools: Preface">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html 1.76">
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.sansserif {font-family:sans-serif; font-weight:normal;}
+ul.toc {list-style: none}
+-->
+</style>
-</HEAD>
-<BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
+</head>
-<A NAME="SEC_Top"></A>
-<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
-<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
-</TR></TABLE>
-<H1>Learning the GNU development tools</H1></P><P>
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC1">Preface</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC2">Acknowledgements</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC3">Copying</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC4">1. Installing GNU software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC10">2. Writing Good Programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC18">3. Using GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC30">4. Compiling with Makefiles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC39">5. The GNU build system</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC50">6. Using Automake and Autoconf</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC67">7. Using Libtool</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC68">8. Using Autotoolset</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC77">9. Using C and C++ effectively</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC78">10. Using Fortran effectively</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC86">11. Internationalization</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC87">12. Maintaining Documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC97">13. Portable shell programming</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC98">14. Writing Autoconf macros</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC99">A. Legal issues with Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC104">B. Philosophical issues</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC113">C. Licensing Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC117">D. GNU GENERAL PUBLIC LICENSE</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[ < ]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[ << ]</td>
+<td valign="middle" align="left">[ Up ]</td>
+<td valign="middle" align="left">[<a href="#SEC2" title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#SEC1" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[Index]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top"><a href="#SEC1">Preface</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC2">Acknowledgements</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC3">Copying</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC4">1. Installing GNU software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC10">2. Writing Good Programs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC18">3. Using GNU Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC30">4. Compiling with Makefiles</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC39">5. The GNU build system</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC50">6. Using Automake and Autoconf</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC67">7. Using Libtool</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC68">8. Using Autotoolset</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC77">9. Using C and C++ effectively</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC78">10. Using Fortran effectively</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC86">11. Internationalization</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC87">12. Maintaining Documentation</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC97">13. Portable shell programming</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC98">14. Writing Autoconf macros</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC99">A. Legal issues with Free Software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC104">B. Philosophical issues</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC113">C. Licensing Free Software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC117">D. GNU GENERAL PUBLIC LICENSE</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+ --- The Detailed Node Listing ---
-<br>
- -- The Detailed Node Listing ---
-<br>
+Installing GNU Software
-<br>
-Installing GNU Software
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC5">1.1 Installing a GNU package</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC6">1.2 The Makefile standards</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC7">1.3 Configuration options</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC8">1.4 Doing a VPATH build</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC9">1.5 Making a binary distribution</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Writing Good Programs
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC5">1.1 Installing a GNU package</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC6">1.2 The Makefile standards</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC7">1.3 Configuration options</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC8">1.4 Doing a VPATH build</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC9">1.5 Making a binary distribution</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC11">2.1 Why good code is important</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC12">2.2 Choosing a good programming language</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC13">2.3 Developing libraries</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC14">2.4 Developing applications</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC15">2.5 Free software is good software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC16">2.6 Invoking the <samp>`gpl'</samp> utility</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC17">2.7 Inserting notices with Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Using GNU Emacs
-<br>
-Writing Good Programs
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC19">3.1 Introduction to Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC20">3.2 Installing GNU Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC21">3.3 Basic Emacs concepts</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC22">3.4 Configuring GNU Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC23">3.5 Using vi emulation</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC24">3.6 Navigating source code</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC25">3.7 Using Emacs as an email client</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC26">3.8 Handling patches</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC27">3.9 Inserting copyright notices with Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC28">3.10 Hacker sanity with Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC29">3.11 Further reading on Emacs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Compiling with Makefiles
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC11">2.1 Why good code is important</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC12">2.2 Choosing a good programming language</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC13">2.3 Developing libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC14">2.4 Developing applications</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC15">2.5 Free software is good software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC16">2.6 Invoking the <SAMP>`gpl'</SAMP> utility</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC17">2.7 Inserting notices with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC31">4.1 Compiling simple programs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC32">4.2 Programs with many source files</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC33">4.3 Building libraries</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC34">4.4 Dealing with header files</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC35">4.5 The GPL and libraries</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC36">4.6 The language runtime libraries.</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC37">4.7 Basic Makefile concepts</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC38">4.8 More about Makefiles</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+The GNU build system
-<br>
-Using GNU Emacs
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC40">5.1 Introducing the GNU tools</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC41">5.2 Installing the GNU build system</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC42">5.3 Hello world example with Autoconf and Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC43">5.4 Understanding the hello world example</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC44">5.5 Using configuration headers</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC45">5.6 Maintaining the documentation files</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC46">5.7 Organizing your project in subdirectories</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC47">5.8 Applying the GPL</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC48">5.9 Handling version numbers</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC49">5.10 Hello world with acmkdir</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Using Automake and Autoconf
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC19">3.1 Introduction to Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC20">3.2 Installing GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC21">3.3 Basic Emacs concepts</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC22">3.4 Configuring GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC23">3.5 Using vi emulation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC24">3.6 Navigating source code</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC25">3.7 Using Emacs as an email client</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC26">3.8 Handling patches</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC27">3.9 Inserting copyright notices with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC28">3.10 Hacker sanity with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC29">3.11 Further reading on Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC51">6.1 Hello World revisited</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC52">6.2 OLD Using configuration headers</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC53">6.3 The building process</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC54">6.4 Some general advice</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC55">6.5 Standard organization with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC56">6.6 Programs and Libraries with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC57">6.7 General Automake principles</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC58">6.8 Simple Automake examples</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC59">6.9 Libraries with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC60">6.10 Dealing with built sources</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC61">6.11 Embedded text with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC62">6.12 Installation standard directories</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC63">6.13 Scripts with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC64">6.14 Emacs Lisp with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC65">6.15 Guile with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC66">6.16 Data files with Automake</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Using Libtool
-<br>
-Compiling with Makefiles
-<br>
+Using Autotoolset
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC31">4.1 Compiling simple programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC32">4.2 Programs with many source files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC33">4.3 Building libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC34">4.4 Dealing with header files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC35">4.5 The GPL and libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC36">4.6 The language runtime libraries.</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC37">4.7 Basic Makefile concepts</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC38">4.8 More about Makefiles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC69">8.1 Introduction</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC70">8.2 Compiler configuration with the <code>LF</code> macros</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC71">8.3 The features of <samp>`LF_CPP_PORTABILITY'</samp></a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC72">8.4 Writing portable C++</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC73">8.5 Hello world revisited again</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC74">8.6 Invoking <samp>`acmkdir'</samp></a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC75">8.7 Handling Embedded text</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC76">8.8 Handling very deep packages</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Using C and C++ effectively
-<br>
-The GNU build system
-<br>
+Using Fortran effectively
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC40">5.1 Introducing the GNU tools</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC41">5.2 Installing the GNU build system</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC42">5.3 Hello world example with Autoconf and Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC43">5.4 Understanding the hello world example</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC44">5.5 Using configuration headers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC45">5.6 Maintaining the documentation files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC46">5.7 Organizing your project in subdirectories</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC47">5.8 Applying the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC48">5.9 Handling version numbers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC49">5.10 Hello world with acmkdir</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-
-<br>
-Using Automake and Autoconf
-<br>
-
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC51">6.1 Hello World revisited</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC52">6.2 OLD Using configuration headers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC53">6.3 The building process</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC54">6.4 Some general advice</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC55">6.5 Standard organization with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC56">6.6 Programs and Libraries with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC57">6.7 General Automake principles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC58">6.8 Simple Automake examples</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC59">6.9 Libraries with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC60">6.10 Dealing with built sources</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC61">6.11 Embedded text with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC62">6.12 Installation standard directories</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC63">6.13 Scripts with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC64">6.14 Emacs Lisp with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC65">6.15 Guile with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC66">6.16 Data files with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-
-<br>
-Using Libtool
-<br>
-
-<br>
-Using Autotoolset
-<br>
-
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC69">8.1 Introduction</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC70">8.2 Compiler configuration with the <CODE>LF</CODE> macros</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC71">8.3 The features of <SAMP>`LF_CPP_PORTABILITY'</SAMP></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC72">8.4 Writing portable C++</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC73">8.5 Hello world revisited again</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC74">8.6 Invoking <SAMP>`acmkdir'</SAMP></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC75">8.7 Handling Embedded text</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC76">8.8 Handling very deep packages</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-
-<br>
-Using C and C++ effectively
-<br>
-
-<br>
-Using Fortran effectively
-<br>
-
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC79">10.1 Introduction to Fortran support</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC80">10.2 Fortran compilers and linkage</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC81">10.3 Walkthrough a simple example</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC82">10.4 The gory details</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC83">10.5 Portability problems with Fortran</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC79">10.1 Introduction to Fortran support</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC80">10.2 Fortran compilers and linkage</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC81">10.3 Walk through a simple example</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC82">10.4 The gory details</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC83">10.5 Portability problems with Fortran</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Internationalization
-<br>
-<br>
-Maintaining Documentation
-<br>
+Maintaining Documentation
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC88">12.1 Browsing documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC89">12.2 Writing proper manuals</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC90">12.3 Introduction to Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC91">12.4 Markup in Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC92">12.5 GNU Emacs support for Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC93">12.6 Writing man pages</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC94">12.7 Writing documentation with LaTeX</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC95">12.8 Creating a LaTeX package</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC96">12.9 Further reading about LaTeX</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC88">12.1 Browsing documentation</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC89">12.2 Writing proper manuals</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC90">12.3 Introduction to Texinfo</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC91">12.4 Markup in Texinfo</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC92">12.5 GNU Emacs support for Texinfo</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC93">12.6 Writing man pages</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC94">12.7 Writing documentation with LaTeX</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC95">12.8 Creating a LaTeX package</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC96">12.9 Further reading about LaTeX</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Portable shell programming
-<br>
-Portable shell programming
-<br>
+Writing Autoconf macros
-<br>
-Writing Autoconf macros
-<br>
+Legal issues with Free Software
-<br>
-Legal issues with Free Software
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC100">A.1 Understanding Copyright</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC101">A.2 Software patents</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC102">A.3 Export restrictions on encryption software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC103">A.4 Freeing your software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Philosophical issues
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC100">A.1 Understanding Copyright</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC101">A.2 Software patents</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC102">A.3 Export restrictions on encryption software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC103">A.4 Freeing your software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC105">B.1 The Right to Read</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC106">B.2 What is Free Software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC107">B.3 Why software should not have owners</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC108">B.4 Why free software needs free documentation</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC109">B.5 Copyleft; Pragmatic Idealism</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC110">B.6 The X Windows Trap</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC111">B.7 Categories of software</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC112">B.8 Confusing words</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+Licensing Free Software
-<br>
-Philosophical issues
-<br>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC114">C.1 What is Copyleft</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC115">C.2 Why you should use the GPL</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC116">C.3 The LGPL vs the GPL</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+GNU GENERAL PUBLIC LICENSE
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC105">B.1 The Right to Read</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC106">B.2 What is Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC107">B.3 Why software should not have owners</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC108">B.4 Why free software needs free documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC109">B.5 Copyleft; Pragmatic Idealism</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC110">B.6 The X Windows Trap</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC111">B.7 Categories of software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC112">B.8 Confusing words</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
+</pre></th></tr><tr><td align="left" valign="top"><a href="#SEC118">D.1 Preamble</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC119">D.2 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top"><a href="#SEC120">D.3 Appendix: How to Apply These Terms to Your New Programs</a></td><td> </td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
+</pre></th></tr></table>
-<br>
-Licensing Free Software
-<br>
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC114">C.1 What is Copyleft</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC115">C.2 Why you should use the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC116">C.3 The LGPL vs the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-<br>
-GNU GENERAL PUBLIC LICENSE
-<br>
-<br>
-<TABLE BORDER=0 CELLSPACING=0>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC118">D.1 Preamble</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC119">D.2 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC120">D.3 Appendix: How to Apply These Terms to Your New Programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
-</TABLE>
-<br>
-</BLOCKQUOTE>
-<P>
-<HR SIZE=1>
-<A NAME="SEC1"></A>
-<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
-<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> < </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> > </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> << </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> >> </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
-</TR></TABLE>
-<A NAME="Preface"></A>
-<H1> Preface </H1>
-<!--docid::SEC1::-->
-<P>
+<a name="Preface"></a>
+<a name="SEC1"></a>
+<h1 class="unnumbered"> Preface </h1>
-The purpose of this document is to introduce you to the GNU build system,
+<p>The purpose of this document is to introduce you to the GNU build system,
and show you how to use it to write good code.
It also discusses peripheral
topics such as how to use GNU Emacs as a source code navigator, how
@@ -312,13 +365,12 @@
be a software developer who knows his programming languages, and
wants to learn how to package his programs in a way that follows the
GNU coding standards.
-</P><P>
+</p>
-This manual introduces you to the GNU build system and showes you how
+<p>This manual introduces you to the GNU build system and shows you how
to develop high-quality
-</P><P>
-
-This manual shows you how to develop high-quality software on GNU using
+</p>
+<p>This manual shows you how to develop high-quality software on GNU using
the GNU build system that conforms to the GNU coding standards.
These techniques are also useful for software development on GNU/Linux
and most variants of the Unix system. In fact, one of the reasons
@@ -327,127 +379,120 @@
We also discuss peripheral topics such as how to use GNU
Emacs as an IDE (integrated development environment), and the various
practical, legal and philosophical concerns behind software development.
-</P><P>
-
-When we speak of the <EM>GNU build system</EM> we refer primarily to the
+</p>
+<p>When we speak of the <em>GNU build system</em> we refer primarily to the
following four packages:
-<UL>
-<LI>
-<STRONG>Autoconf</STRONG> produces a <EM>configuration shell script</EM>, named
-<TT>`configure'</TT>, which probes the installer platform for portability related
+</p><ul>
+<li>
+<strong>Autoconf</strong> produces a <em>configuration shell script</em>, named
+<tt>`configure'</tt>, which probes the installer platform for portability related
information which is required to customize makefiles, configuration header
files, and other application specific files. Then it proceeds to generate
customized versions of these files from generic templates. This way, the
user will not need to customize these files manually.
-<LI>
-<STRONG>Automake</STRONG> produces makefile templates, <TT>`Makefile.in'</TT> to be used
+</li><li>
+<strong>Automake</strong> produces makefile templates, <tt>`Makefile.in'</tt> to be used
by Autoconf, from a very high level specification stored in a file called
-<TT>`Makefile.am'</TT>. Automake produces makefiles that conform to the GNU
+<tt>`Makefile.am'</tt>. Automake produces makefiles that conform to the GNU
makefile standards, taking away the extraordinary effort required to produce
them by hand. Automake requires Autoconf in order to be used properly.
-<LI>
-<STRONG>Libtool</STRONG> makes it possible to compile position indepedent code and
+</li><li>
+<strong>Libtool</strong> makes it possible to compile position independent code and
build shared libraries in a portable manner. It does not require either
-Autoconf, or Automake and can be used indepedently. Automake however supports
+Autoconf, or Automake and can be used independently. Automake however supports
libtool and interoperates with it in a seamless manner.
-<LI>
-<STRONG>Autotoolset</STRONG>
-<EM>FIXME: Add content</EM>
-</UL>
-<P>
+</li><li>
+<strong>Autotoolset</strong>
+<em>FIXME: Add content</em>
+</li></ul>
-The GNU build system has two goals. The first is to simplify the development
+<p>The GNU build system has two goals. The first is to simplify the development
of portable programs. The second is to simplify the building of programs that
are distributed as source code. The first goal is achieved by the automatic
-generation of a <TT>`configure'</TT> shell script. The second goal is achieved
+generation of a <tt>`configure'</tt> shell script. The second goal is achieved
by the automatic generation of Makefiles and other shell scripts that are
typically used in the building process. This way the developer can concentrate
on debugging his source code, instead of his overly complex Makefiles.
And the installer can compile and install the program directly from the
source code distribution by a simple and automatic procedure.
-</P><P>
-
-The GNU build system needs to be installed only when you are developing
+</p>
+<p>The GNU build system needs to be installed only when you are developing
programs that are meant to be distributed. To build a program from
-distributed source code, you only need a working <CODE>make</CODE>, a compiler,
+distributed source code, you only need a working <code>make</code>, a compiler,
a shell,
-and sometimes standard Unix utilities like <CODE>sed</CODE>, <CODE>awk</CODE>,
-<CODE>yacc</CODE>, <CODE>lex</CODE>. The objective is to make software installation
+and sometimes standard Unix utilities like <code>sed</code>, <code>awk</code>,
+<code>yacc</code>, <code>lex</code>. The objective is to make software installation
as simple and as automatic as possible for the installer. Also, by
setting up the GNU build system such that it creates programs that don't
require the build system to be present during their installation, it
becomes possible to use the build system to bootstrap itself.
-</P><P>
-
-Some tasks that are simplified by the GNU build system include:
-<UL>
-<LI>
-Building multidirectory software packages. It is much more difficult to use
-raw <CODE>make</CODE> recursively. Having simplified this step, the developer
+</p>
+<p>Some tasks that are simplified by the GNU build system include:
+</p><ul>
+<li>
+Building multi directory software packages. It is much more difficult to use
+raw <code>make</code> recursively. Having simplified this step, the developer
is encouraged to organize his source code in a deep directory tree rather than
-lump everything under the same directory. Developers that use raw <CODE>make</CODE>
+lump everything under the same directory. Developers that use raw <code>make</code>
often can't justify the inconvenience of recursive make and prefer to
disorganize their source code. With the GNU tools this is no longer necessary.
-<LI>
+</li><li>
Automatic configuration. You will never have to tell your users that they
need to edit your Makefile. You yourself will not have to edit your Makefiles
as you move new versions of your code back and forth between different
machines.
-<LI>
+</li><li>
Automatic makefile generation. Writing makefiles involves a lot of repetition,
and in large projects it will get on your nerves. The GNU build system
-instead requires you to write <TT>`Makefile.am'</TT> files that are much more terse
+instead requires you to write <tt>`Makefile.am'</tt> files that are much more terse
and easy to maintain.
-<LI>
+</li><li>
Support for test suites. You can very easily write test suite code, and
-by adding one extra line in your <TT>`Makefile.am'</TT> make a <CODE>check</CODE>
+by adding one extra line in your <tt>`Makefile.am'</tt> make a <code>check</code>
target available such that you can compile and run the entire test suite
-by running <CODE>make check</CODE>.
-<LI>
+by running <code>make check</code>.
+</li><li>
Automatic distribution building. The GNU build tools are meant to be used
-in the development of <EM>free software</EM>, therefore if you have a working
+in the development of <em>free software</em>, therefore if you have a working
build system in place for your programs, you can create a source code
distribution out of
-it by running <CODE>make distcheck</CODE>.
-<LI>
+it by running <code>make distcheck</code>.
+</li><li>
Shared libraries. Building shared libraries becomes as easy as building
static libraries.
-</UL>
-<P>
+</li></ul>
-The Autotoolset package complements the GNU build system by providing the
+<p>The Autotoolset package complements the GNU build system by providing the
following additional features:
-<UL>
-<LI>
+</p><ul>
+<li>
Automatic generation of legal notices that are needed in order to
apply the GNU GPL license.
-<LI>
+</li><li>
Automatic generation of directory trees for new software packages, such that
they conform to the GNITS standard (more or less).
-<LI>
+</li><li>
Some rudimentary portability framework for C++ programs. There is a lot
of room for improvement here, in the future. Also a framework for
-embedding text into your executable and handling include files accross
+embedding text into your executable and handling include files across
multiple directories.
-<LI>
+</li><li>
Support for writing portable software that uses both Fortran and C++.
-<LI>
+</li><li>
Additional support for writing software documentation in Texinfo, but also in
LaTeX.
-</UL>
-Autotoolset is still under development and there may still be bugs. At the
+</li></ul>
+<p>Autotoolset is still under development and there may still be bugs. At the
moment Autotoolset doesn't do shared libraries, but that will change in the
future.
-<P>
-
-This effort began by my attempt to write a tutorial for Autoconf. It involved
-into <EM>"Learning Autoconf and Automake"</EM>. Along the way I developed
+</p>
+<p>This effort began by my attempt to write a tutorial for Autoconf. It involved
+into <em>"Learning Autoconf and Automake"</em>. Along the way I developed
Autotoolset to deal with things that annoyed me or to cover needs from my
own work. Ultimately I want this document to be both a unified introduction of
the GNU build system as well as documentation for the Autotoolset package.
-</P><P>
-
-I believe that knowing these tools and having this know-how is very important,
+</p>
+<p>I believe that knowing these tools and having this know-how is very important,
and should not be missed from engineering or science students who will one
day go out and do software development for academic or industrial research.
Many students are incredibly
@@ -462,706 +507,739 @@
people get over the learning curve of the second step, so they can be
productive and ready to study the reference manuals that are distributed
with all these tools.
-</P><P>
-
-This manual of course is still under construction. When I am done constructing
+</p>
+<p>This manual of course is still under construction. When I am done constructing
it some paragraph somewhere will be inserted with the traditional run-down of
summaries about each chapter. I write this manual in a highly non-linear
way, so while it is under construction you will find that some parts
are better-developed than others. If you wish to contribute sections of
the manual that I haven't written or haven't yet developed fully, please
contact me.
-</P><P>
-
-Chapters 1,2,3,4 are okey. Chapter 5 is okey to, but needs a little more
+</p>
+<p>Chapters 1,2,3,4 are okay. Chapter 5 is okay to, but needs a little more
work. I removed the other chapters to minimize confusion, but the sources
for them are still being distributed as part of the Autotoolset package
for those that found them useful. The other chapters need a lot of rewriting
and they would do more harm than good at this point to the unsuspecting reader.
Please contact me if you have any suggestions
for improving this manual.
-</P><P>
-
-Remarks by Marcelo: I am currentrly updating this manual to the last release
+</p>
+<p>Remarks by Marcelo: I am currently updating this manual to the last release
of the autoconf/automake tools.
-</P><P>
+</p>
-<A NAME="Acknowledgements"></A>
-<HR SIZE="6">
-<A NAME="SEC2"></A>
-<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
-<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC1"> < </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> > </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC1"> << </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> >> </A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
-<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
-</TR></TABLE>
-<H1> Acknowledgements </H1>
-<!--docid::SEC2::-->
-<P>
+<hr size="6">
+<a name="Acknowledgements"></a>
+<a name="SEC2"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#SEC1" title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#SEC1" title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#SEC3" title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#SEC1" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Conte...
[truncated message content] |
|
From: <mro...@us...> - 2007-05-14 16:59:42
|
Revision: 45
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=45&view=rev
Author: mroberto
Date: 2007-05-14 09:59:41 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Update of home page.
Modified Paths:
--------------
htdocs/index.shtml
Modified: htdocs/index.shtml
===================================================================
--- htdocs/index.shtml 2007-05-14 16:51:10 UTC (rev 44)
+++ htdocs/index.shtml 2007-05-14 16:59:41 UTC (rev 45)
@@ -1,99 +1,110 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
- <meta name="Author" content="Marcelo Roberto Jimenez" />
- <meta name="copyright" content="Copyright(c) Marcelo Roberto Jimenez" />
- <meta name="Description" content="Home Page of Autotoolset" />
- <title>Welcome to Autotoolset Home Page!</title>
- <!-- If you use CSS2 in the same file, use style, otherwise, use link -->
- <link href="index.css" rel="stylesheet" type="text/css" />
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <meta name="Author" content="Marcelo Roberto Jimenez" />
+ <meta name="copyright" content="Copyright(c) Marcelo Roberto Jimenez" />
+ <meta name="Description" content="Home Page of Autotoolset" />
+ <title>Welcome to Autotoolset Home Page!</title>
+ <!-- If you use CSS2 in the same file, use style, otherwise, use link -->
+ <link href="index.css" rel="stylesheet" type="text/css" />
</head>
<body>
- <hr class="half" />
+<hr class="half" />
- <h1>
- <a href="http://www.gnu.org" >
- <img style="width:129;height:122;border:0" src="gnu-head-sm.jpg" alt=" [image of the Head of a GNU] "/>
- </a>
- </h1>
- <h1>
- Welcome to Autotoolset Home Page!
- </h1>
+<h1>
+ <a href="http://www.gnu.org" ><img style="width:129;height:122;border:0"
+ src="gnu-head-sm.jpg" alt=" [image of the Head of a GNU] " /></a>
+</h1>
+<h1>
+ Welcome to Autotoolset Home Page!
+</h1>
- <hr class="half" />
+<hr class="half" />
- <p>
- The Autotoolset package (former autotools package) complements the GNU build system by providing the following features:
- </p>
- <ul>
- <li>
- Automatic generation of legal notices that are needed in order to apply the GNU GPL license
- </li>
- <li>
- Automatic generation of directory trees for new software packages, such that they conform to the GNITS standard (more or less).
- </li>
- <li>
- Some rudimentary portability framework for C++ programs. There is a lot of room for improvement here, in the future. Also a framework for embedding text into your executable and handling include files accross multiple directories.
- </li>
- <li>
- Support for writing portable software that uses both Fortran and C++.
- </li>
- <li>
- Additional support for writing software documentation in Texinfo, but also in LaTeX.
- </li>
- <li>
- A manual introducing both Autotools and the GNU build system in a unified task-oriented manner.
- </li>
- </ul>
+<p>
+The Autotoolset package (former autotools package) complements the GNU
+build system by providing the following features:
+</p>
+<ul>
+ <li>
+ Automatic generation of legal notices that are needed in order to apply
+ the GNU GPL license
+ </li>
+ <li>
+ Automatic generation of directory trees for new software packages, such
+ that they conform to the GNITS standard (more or less).
+ </li>
+ <li>
+ Some rudimentary portability framework for C++ programs. There is a lot
+ of room for improvement here, in the future. Also a framework for
+ embedding text into your executable and handling include files accross
+ multiple directories.
+ </li>
+ <li>
+ Support for writing portable software that uses both Fortran and C++.
+ </li>
+ <li>
+ Additional support for writing software documentation in Texinfo, but
+ also in LaTeX.
+ </li>
+ <li>
+ A manual introducing both Autotools and the GNU build system in a
+ unified task-oriented manner.
+ </li>
+</ul>
- <hr class="half" />
+<hr class="half" />
- <h2>
- Note
- </h2>
- <p>
- This home page and all the html documentation are inside the Autotoolset distribution. It is possible to create dvi and pdf files of "tutorial". There are .i386.rpm, .src.rpm and .bz2 versions available. The document "toolsmanual" is no longer beeing maintained, but is still there for historical reasons.
- </p>
+<h2>
+Note
+</h2>
+<p>
+ This home page and all the html documentation are inside the
+ Autotoolset distribution. It is possible to create dvi and pdf
+ files of "tutorial". There are .i386.rpm, .src.rpm and .bz2 versions
+ available. The document "toolsmanual" is no longer beeing maintained,
+ but is still there for historical reasons.
+</p>
- <hr class="half" />
+<hr class="half" />
- <h2>
- Some Links
- </h2>
- <ul>
- <li>
- <a href="http://sourceforge.net/project/showfiles.php?group_id=75790">
- Download the Autotoolset distribution files (.i386.rpm, .src.rpm and .bz2)
- </a>
- </li>
- <li>
- <a href="tutorial.html">
- Learning the GNU development tools
- </a>
- </li>
- <li>
- <a href="http://sourceforge.net/projects/autotoolset/">
- Project page on Source Forge
- </a>
- </li>
- <li>
- <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/autotoolset/">
- CVS web interface
- </a>
- </li>
- <li>
- <a href="http://sourceforge.net/mail/?group_id=75790">
- Mailing lists
- </a>
- </li>
- </ul>
+<h2>
+ Some Links
+</h2>
+<ul>
+ <li>
+ <a href="http://sourceforge.net/project/showfiles.php?group_id=75790">
+ Download the Autotoolset distribution files (.i386.rpm, .src.rpm and .bz2)
+ </a>
+ </li>
+ <li>
+ <a href="tutorial.html">
+ Learning the GNU development tools
+ </a>
+ </li>
+ <li>
+ <a href="http://sourceforge.net/projects/autotoolset/">
+ Project page on Source Forge
+ </a>
+ </li>
+ <li>
+ <a href="http://autotoolset.svn.sourceforge.net/viewvc/autotoolset/">
+ Subversion web interface
+ </a>
+ </li>
+ <li>
+ <a href="http://sourceforge.net/mail/?group_id=75790">
+ Mailing lists
+ </a>
+ </li>
+</ul>
- <!--#include file="rodape.shtml" -->
+<!--#include file="rodape.shtml" -->
</body>
</html>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-14 16:51:13
|
Revision: 44
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=44&view=rev
Author: mroberto
Date: 2007-05-14 09:51:10 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Adding homepage files.
Added Paths:
-----------
htdocs/
htdocs/gnu-head-sm.jpg
htdocs/hg/
htdocs/hg/.htaccess
htdocs/index.css
htdocs/index.shtml
htdocs/rodape.shtml
htdocs/tutorial.html
htdocs/valid-xhtml10.png
htdocs/vcss.png
Added: htdocs/gnu-head-sm.jpg
===================================================================
(Binary files differ)
Property changes on: htdocs/gnu-head-sm.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: htdocs/hg/.htaccess
===================================================================
--- htdocs/hg/.htaccess (rev 0)
+++ htdocs/hg/.htaccess 2007-05-14 16:51:10 UTC (rev 44)
@@ -0,0 +1,4 @@
+
+RewriteEngine On
+RewriteRule (.*) /cgi-bin/hgwebdir.cgi/$1
+
Added: htdocs/index.css
===================================================================
--- htdocs/index.css (rev 0)
+++ htdocs/index.css 2007-05-14 16:51:10 UTC (rev 44)
@@ -0,0 +1,67 @@
+@charset "ISO-8859-1";
+:link {
+ background-color: #CCCCCC;
+ color: #0000CC
+}
+:visited {
+ background-color: #CCCCCC;
+ color: #660066
+}
+:active {
+ background-color: #CCCCCC;
+ color: #FF0000
+}
+body {
+ background-color: #CCCCCC;
+ color: #000000;
+ margin-left: 5%;
+ margin-right: 5%;
+ font-family: Verdana, Helvetica, sans-serif;
+}
+h1, h2, h3, h4, h5, p, ul {
+ font-family: Verdana, Helvetica, sans-serif;
+}
+h1 {
+ text-align: center;
+ font-weight: bold;
+}
+h3 {
+ text-indent: 1em;
+}
+pre {
+ font-family: monospace;
+}
+p {
+ text-indent: 2em;
+ text-align: justify;
+}
+p.centrado {
+ text-align: center;
+}
+p.centritalico {
+ font-style: italic;
+ font-family: serif;
+ font-size: 75%;
+ text-align: center;
+}
+table {
+ font-family: Garamond, "Times New Roman", serif;
+}
+table.rodape {
+ width: 100%;
+}
+hr.half {
+ width: 50%;
+ margin-top: 3ex;
+ margin-bottom: 3ex;
+}
+img.left {
+ float: left;
+}
+ol.RomanoMaiusculo {
+ list-style-type: upper-roman;
+}
+ol.AlfaMinusculo {
+ list-style-type: lower-alpha;
+}
+
Added: htdocs/index.shtml
===================================================================
--- htdocs/index.shtml (rev 0)
+++ htdocs/index.shtml 2007-05-14 16:51:10 UTC (rev 44)
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <meta name="Author" content="Marcelo Roberto Jimenez" />
+ <meta name="copyright" content="Copyright(c) Marcelo Roberto Jimenez" />
+ <meta name="Description" content="Home Page of Autotoolset" />
+ <title>Welcome to Autotoolset Home Page!</title>
+ <!-- If you use CSS2 in the same file, use style, otherwise, use link -->
+ <link href="index.css" rel="stylesheet" type="text/css" />
+</head>
+
+<body>
+
+ <hr class="half" />
+
+ <h1>
+ <a href="http://www.gnu.org" >
+ <img style="width:129;height:122;border:0" src="gnu-head-sm.jpg" alt=" [image of the Head of a GNU] "/>
+ </a>
+ </h1>
+ <h1>
+ Welcome to Autotoolset Home Page!
+ </h1>
+
+ <hr class="half" />
+
+ <p>
+ The Autotoolset package (former autotools package) complements the GNU build system by providing the following features:
+ </p>
+ <ul>
+ <li>
+ Automatic generation of legal notices that are needed in order to apply the GNU GPL license
+ </li>
+ <li>
+ Automatic generation of directory trees for new software packages, such that they conform to the GNITS standard (more or less).
+ </li>
+ <li>
+ Some rudimentary portability framework for C++ programs. There is a lot of room for improvement here, in the future. Also a framework for embedding text into your executable and handling include files accross multiple directories.
+ </li>
+ <li>
+ Support for writing portable software that uses both Fortran and C++.
+ </li>
+ <li>
+ Additional support for writing software documentation in Texinfo, but also in LaTeX.
+ </li>
+ <li>
+ A manual introducing both Autotools and the GNU build system in a unified task-oriented manner.
+ </li>
+ </ul>
+
+ <hr class="half" />
+
+ <h2>
+ Note
+ </h2>
+ <p>
+ This home page and all the html documentation are inside the Autotoolset distribution. It is possible to create dvi and pdf files of "tutorial". There are .i386.rpm, .src.rpm and .bz2 versions available. The document "toolsmanual" is no longer beeing maintained, but is still there for historical reasons.
+ </p>
+
+ <hr class="half" />
+
+ <h2>
+ Some Links
+ </h2>
+ <ul>
+ <li>
+ <a href="http://sourceforge.net/project/showfiles.php?group_id=75790">
+ Download the Autotoolset distribution files (.i386.rpm, .src.rpm and .bz2)
+ </a>
+ </li>
+ <li>
+ <a href="tutorial.html">
+ Learning the GNU development tools
+ </a>
+ </li>
+ <li>
+ <a href="http://sourceforge.net/projects/autotoolset/">
+ Project page on Source Forge
+ </a>
+ </li>
+ <li>
+ <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/autotoolset/">
+ CVS web interface
+ </a>
+ </li>
+ <li>
+ <a href="http://sourceforge.net/mail/?group_id=75790">
+ Mailing lists
+ </a>
+ </li>
+ </ul>
+
+ <!--#include file="rodape.shtml" -->
+
+</body>
+</html>
Added: htdocs/rodape.shtml
===================================================================
--- htdocs/rodape.shtml (rev 0)
+++ htdocs/rodape.shtml 2007-05-14 16:51:10 UTC (rev 44)
@@ -0,0 +1,42 @@
+ <hr />
+
+ <table class="rodape" cellpadding="0" cellspacing="0" border="0">
+ <tbody>
+ <tr>
+ <td style="width:40%" align="left">
+ <address>
+ If you have comments or suggestions,
+ email us at
+ <a href="mailto:mro...@us...">
+ <mro...@us...>
+ </a>
+ or
+ <a href="mailto:hu...@us...">
+ <hu...@us...>
+ </a>
+ </address>
+ </td>
+ <td style="width:60%" align="right">
+ <address>
+ Last updated: $<!--#flastmod file="$DOCUMENT_NAME" --> $
+ </address>
+ <br />
+ </td>
+ </tr>
+ <tr>
+ <td>
+ </td>
+ <td align="right">
+ <a href="http://validator.w3.org/check/referer">
+ <img style="border:0;width:88px;height:31px" src="valid-xhtml10.png" alt="Valid XHTML 1.0!" />
+ </a>
+ <a href="http://jigsaw.w3.org/css-validator/">
+ <img style="border:0;width:88px;height:31px" src="vcss.png" alt="Valid CSS!" />
+ </a>
+ <a href="http://sourceforge.net">
+ <img style="width:88;height:31;border:0" src="http://sourceforge.net/sflogo.php?group_id=75790&type=1" alt="SourceForge.net Logo" />
+ </a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
Added: htdocs/tutorial.html
===================================================================
--- htdocs/tutorial.html (rev 0)
+++ htdocs/tutorial.html 2007-05-14 16:51:10 UTC (rev 44)
@@ -0,0 +1,13760 @@
+<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<!-- Created on January, 10 2005 by texi2html 1.64 -->
+<!--
+Written by: Lionel Cons <Lio...@ce...> (original author)
+ Karl Berry <ka...@fr...>
+ Olaf Bachmann <oba...@ma...>
+ and many others.
+Maintained by: Olaf Bachmann <oba...@ma...>
+Send bugs and suggestions to <tex...@ma...>
+
+-->
+<HEAD>
+<TITLE>Learning the GNU development tools: </TITLE>
+
+<META NAME="description" CONTENT="Learning the GNU development tools: ">
+<META NAME="keywords" CONTENT="Learning the GNU development tools: ">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+<META NAME="Generator" CONTENT="texi2html 1.64">
+
+</HEAD>
+
+<BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
+
+<A NAME="SEC_Top"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H1>Learning the GNU development tools</H1></P><P>
+
+<BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC1">Preface</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC2">Acknowledgements</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC3">Copying</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC4">1. Installing GNU software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC10">2. Writing Good Programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC18">3. Using GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC30">4. Compiling with Makefiles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC39">5. The GNU build system</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC50">6. Using Automake and Autoconf</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC67">7. Using Libtool</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC68">8. Using Autotoolset</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC77">9. Using C and C++ effectively</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC78">10. Using Fortran effectively</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC86">11. Internationalization</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC87">12. Maintaining Documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC97">13. Portable shell programming</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC98">14. Writing Autoconf macros</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC99">A. Legal issues with Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC104">B. Philosophical issues</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC113">C. Licensing Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC117">D. GNU GENERAL PUBLIC LICENSE</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+ -- The Detailed Node Listing ---
+<br>
+
+<br>
+Installing GNU Software
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC5">1.1 Installing a GNU package</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC6">1.2 The Makefile standards</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC7">1.3 Configuration options</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC8">1.4 Doing a VPATH build</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC9">1.5 Making a binary distribution</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Writing Good Programs
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC11">2.1 Why good code is important</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC12">2.2 Choosing a good programming language</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC13">2.3 Developing libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC14">2.4 Developing applications</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC15">2.5 Free software is good software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC16">2.6 Invoking the <SAMP>`gpl'</SAMP> utility</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC17">2.7 Inserting notices with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Using GNU Emacs
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC19">3.1 Introduction to Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC20">3.2 Installing GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC21">3.3 Basic Emacs concepts</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC22">3.4 Configuring GNU Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC23">3.5 Using vi emulation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC24">3.6 Navigating source code</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC25">3.7 Using Emacs as an email client</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC26">3.8 Handling patches</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC27">3.9 Inserting copyright notices with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC28">3.10 Hacker sanity with Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC29">3.11 Further reading on Emacs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Compiling with Makefiles
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC31">4.1 Compiling simple programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC32">4.2 Programs with many source files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC33">4.3 Building libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC34">4.4 Dealing with header files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC35">4.5 The GPL and libraries</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC36">4.6 The language runtime libraries.</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC37">4.7 Basic Makefile concepts</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC38">4.8 More about Makefiles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+The GNU build system
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC40">5.1 Introducing the GNU tools</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC41">5.2 Installing the GNU build system</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC42">5.3 Hello world example with Autoconf and Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC43">5.4 Understanding the hello world example</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC44">5.5 Using configuration headers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC45">5.6 Maintaining the documentation files</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC46">5.7 Organizing your project in subdirectories</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC47">5.8 Applying the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC48">5.9 Handling version numbers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC49">5.10 Hello world with acmkdir</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Using Automake and Autoconf
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC51">6.1 Hello World revisited</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC52">6.2 OLD Using configuration headers</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC53">6.3 The building process</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC54">6.4 Some general advice</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC55">6.5 Standard organization with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC56">6.6 Programs and Libraries with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC57">6.7 General Automake principles</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC58">6.8 Simple Automake examples</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC59">6.9 Libraries with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC60">6.10 Dealing with built sources</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC61">6.11 Embedded text with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC62">6.12 Installation standard directories</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC63">6.13 Scripts with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC64">6.14 Emacs Lisp with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC65">6.15 Guile with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC66">6.16 Data files with Automake</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Using Libtool
+<br>
+
+<br>
+Using Autotoolset
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC69">8.1 Introduction</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC70">8.2 Compiler configuration with the <CODE>LF</CODE> macros</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC71">8.3 The features of <SAMP>`LF_CPP_PORTABILITY'</SAMP></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC72">8.4 Writing portable C++</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC73">8.5 Hello world revisited again</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC74">8.6 Invoking <SAMP>`acmkdir'</SAMP></A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC75">8.7 Handling Embedded text</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC76">8.8 Handling very deep packages</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Using C and C++ effectively
+<br>
+
+<br>
+Using Fortran effectively
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC79">10.1 Introduction to Fortran support</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC80">10.2 Fortran compilers and linkage</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC81">10.3 Walkthrough a simple example</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC82">10.4 The gory details</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC83">10.5 Portability problems with Fortran</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Internationalization
+<br>
+
+<br>
+Maintaining Documentation
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC88">12.1 Browsing documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC89">12.2 Writing proper manuals</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC90">12.3 Introduction to Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC91">12.4 Markup in Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC92">12.5 GNU Emacs support for Texinfo</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC93">12.6 Writing man pages</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC94">12.7 Writing documentation with LaTeX</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC95">12.8 Creating a LaTeX package</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC96">12.9 Further reading about LaTeX</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Portable shell programming
+<br>
+
+<br>
+Writing Autoconf macros
+<br>
+
+<br>
+Legal issues with Free Software
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC100">A.1 Understanding Copyright</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC101">A.2 Software patents</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC102">A.3 Export restrictions on encryption software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC103">A.4 Freeing your software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Philosophical issues
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC105">B.1 The Right to Read</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC106">B.2 What is Free Software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC107">B.3 Why software should not have owners</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC108">B.4 Why free software needs free documentation</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC109">B.5 Copyleft; Pragmatic Idealism</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC110">B.6 The X Windows Trap</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC111">B.7 Categories of software</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC112">B.8 Confusing words</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+Licensing Free Software
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC114">C.1 What is Copyleft</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC115">C.2 Why you should use the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC116">C.3 The LGPL vs the GPL</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+GNU GENERAL PUBLIC LICENSE
+<br>
+
+<br>
+<TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC118">D.1 Preamble</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC119">D.2 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC120">D.3 Appendix: How to Apply These Terms to Your New Programs</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE>
+
+<br>
+</BLOCKQUOTE>
+<P>
+
+<HR SIZE=1>
+<A NAME="SEC1"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<A NAME="Preface"></A>
+<H1> Preface </H1>
+<!--docid::SEC1::-->
+<P>
+
+The purpose of this document is to introduce you to the GNU build system,
+and show you how to use it to write good code.
+It also discusses peripheral
+topics such as how to use GNU Emacs as a source code navigator, how
+to write good software, and the philosophical concerns behind the free
+software movement. The intended reader should
+be a software developer who knows his programming languages, and
+wants to learn how to package his programs in a way that follows the
+GNU coding standards.
+</P><P>
+
+This manual introduces you to the GNU build system and showes you how
+to develop high-quality
+</P><P>
+
+This manual shows you how to develop high-quality software on GNU using
+the GNU build system that conforms to the GNU coding standards.
+These techniques are also useful for software development on GNU/Linux
+and most variants of the Unix system. In fact, one of the reasons
+for the elaborate GNU build system was to make software portable between
+GNU and other similar operating systems.
+We also discuss peripheral topics such as how to use GNU
+Emacs as an IDE (integrated development environment), and the various
+practical, legal and philosophical concerns behind software development.
+</P><P>
+
+When we speak of the <EM>GNU build system</EM> we refer primarily to the
+following four packages:
+<UL>
+<LI>
+<STRONG>Autoconf</STRONG> produces a <EM>configuration shell script</EM>, named
+<TT>`configure'</TT>, which probes the installer platform for portability related
+information which is required to customize makefiles, configuration header
+files, and other application specific files. Then it proceeds to generate
+customized versions of these files from generic templates. This way, the
+user will not need to customize these files manually.
+<LI>
+<STRONG>Automake</STRONG> produces makefile templates, <TT>`Makefile.in'</TT> to be used
+by Autoconf, from a very high level specification stored in a file called
+<TT>`Makefile.am'</TT>. Automake produces makefiles that conform to the GNU
+makefile standards, taking away the extraordinary effort required to produce
+them by hand. Automake requires Autoconf in order to be used properly.
+<LI>
+<STRONG>Libtool</STRONG> makes it possible to compile position indepedent code and
+build shared libraries in a portable manner. It does not require either
+Autoconf, or Automake and can be used indepedently. Automake however supports
+libtool and interoperates with it in a seamless manner.
+<LI>
+<STRONG>Autotoolset</STRONG>
+<EM>FIXME: Add content</EM>
+</UL>
+<P>
+
+The GNU build system has two goals. The first is to simplify the development
+of portable programs. The second is to simplify the building of programs that
+are distributed as source code. The first goal is achieved by the automatic
+generation of a <TT>`configure'</TT> shell script. The second goal is achieved
+by the automatic generation of Makefiles and other shell scripts that are
+typically used in the building process. This way the developer can concentrate
+on debugging his source code, instead of his overly complex Makefiles.
+And the installer can compile and install the program directly from the
+source code distribution by a simple and automatic procedure.
+</P><P>
+
+The GNU build system needs to be installed only when you are developing
+programs that are meant to be distributed. To build a program from
+distributed source code, you only need a working <CODE>make</CODE>, a compiler,
+a shell,
+and sometimes standard Unix utilities like <CODE>sed</CODE>, <CODE>awk</CODE>,
+<CODE>yacc</CODE>, <CODE>lex</CODE>. The objective is to make software installation
+as simple and as automatic as possible for the installer. Also, by
+setting up the GNU build system such that it creates programs that don't
+require the build system to be present during their installation, it
+becomes possible to use the build system to bootstrap itself.
+</P><P>
+
+Some tasks that are simplified by the GNU build system include:
+<UL>
+<LI>
+Building multidirectory software packages. It is much more difficult to use
+raw <CODE>make</CODE> recursively. Having simplified this step, the developer
+is encouraged to organize his source code in a deep directory tree rather than
+lump everything under the same directory. Developers that use raw <CODE>make</CODE>
+often can't justify the inconvenience of recursive make and prefer to
+disorganize their source code. With the GNU tools this is no longer necessary.
+<LI>
+Automatic configuration. You will never have to tell your users that they
+need to edit your Makefile. You yourself will not have to edit your Makefiles
+as you move new versions of your code back and forth between different
+machines.
+<LI>
+Automatic makefile generation. Writing makefiles involves a lot of repetition,
+and in large projects it will get on your nerves. The GNU build system
+instead requires you to write <TT>`Makefile.am'</TT> files that are much more terse
+and easy to maintain.
+<LI>
+Support for test suites. You can very easily write test suite code, and
+by adding one extra line in your <TT>`Makefile.am'</TT> make a <CODE>check</CODE>
+target available such that you can compile and run the entire test suite
+by running <CODE>make check</CODE>.
+<LI>
+Automatic distribution building. The GNU build tools are meant to be used
+in the development of <EM>free software</EM>, therefore if you have a working
+build system in place for your programs, you can create a source code
+distribution out of
+it by running <CODE>make distcheck</CODE>.
+<LI>
+Shared libraries. Building shared libraries becomes as easy as building
+static libraries.
+</UL>
+<P>
+
+The Autotoolset package complements the GNU build system by providing the
+following additional features:
+<UL>
+<LI>
+Automatic generation of legal notices that are needed in order to
+apply the GNU GPL license.
+<LI>
+Automatic generation of directory trees for new software packages, such that
+they conform to the GNITS standard (more or less).
+<LI>
+Some rudimentary portability framework for C++ programs. There is a lot
+of room for improvement here, in the future. Also a framework for
+embedding text into your executable and handling include files accross
+multiple directories.
+<LI>
+Support for writing portable software that uses both Fortran and C++.
+<LI>
+Additional support for writing software documentation in Texinfo, but also in
+LaTeX.
+</UL>
+Autotoolset is still under development and there may still be bugs. At the
+moment Autotoolset doesn't do shared libraries, but that will change in the
+future.
+<P>
+
+This effort began by my attempt to write a tutorial for Autoconf. It involved
+into <EM>"Learning Autoconf and Automake"</EM>. Along the way I developed
+Autotoolset to deal with things that annoyed me or to cover needs from my
+own work. Ultimately I want this document to be both a unified introduction of
+the GNU build system as well as documentation for the Autotoolset package.
+</P><P>
+
+I believe that knowing these tools and having this know-how is very important,
+and should not be missed from engineering or science students who will one
+day go out and do software development for academic or industrial research.
+Many students are incredibly
+undertrained in software engineering and write a lot of bad code.
+This is very very sad because of all people, it is them that have the
+greatest need to write portable, robust and reliable code. I found from
+my own experience that moving away from Fortran and C, and towards C++
+is the first step in writing better code. The second step is to use
+the sophisticated GNU build system and use it properly, as described
+in this document.
+Ultimately, I am hoping that this document will help
+people get over the learning curve of the second step, so they can be
+productive and ready to study the reference manuals that are distributed
+with all these tools.
+</P><P>
+
+This manual of course is still under construction. When I am done constructing
+it some paragraph somewhere will be inserted with the traditional run-down of
+summaries about each chapter. I write this manual in a highly non-linear
+way, so while it is under construction you will find that some parts
+are better-developed than others. If you wish to contribute sections of
+the manual that I haven't written or haven't yet developed fully, please
+contact me.
+</P><P>
+
+Chapters 1,2,3,4 are okey. Chapter 5 is okey to, but needs a little more
+work. I removed the other chapters to minimize confusion, but the sources
+for them are still being distributed as part of the Autotoolset package
+for those that found them useful. The other chapters need a lot of rewriting
+and they would do more harm than good at this point to the unsuspecting reader.
+Please contact me if you have any suggestions
+for improving this manual.
+</P><P>
+
+Remarks by Marcelo: I am currentrly updating this manual to the last release
+of the autoconf/automake tools.
+</P><P>
+
+<A NAME="Acknowledgements"></A>
+<HR SIZE="6">
+<A NAME="SEC2"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC1"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC1"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H1> Acknowledgements </H1>
+<!--docid::SEC2::-->
+<P>
+
+This document and the Autotools package have originally been written by
+Eleftherios Gkioulekas. Many people have further contributed to this
+effort, directly or indirectly, in various way. Here is a list of these
+people. Please help me keep it complete and exempt of errors.
+</P><P>
+
+<UL>
+<LI>
+<A HREF="tutorial.html#SEC104">B. Philosophical issues</A>, and <A HREF="tutorial.html#SEC113">C. Licensing Free Software</A>,
+were written by Richard Stallman. Richard has also contributed many useful
+review comments and helped me with the legal paperwork.
+The appendix <EM>Philosophical issues</EM>
+has been written by Richard Stallman.
+(see section <A HREF="tutorial.html#SEC104">B. Philosophical issues</A>)
+<LI>
+The chapter on Fortran, and the Autotools support for developing software
+that is partly written in Fortran is derived from the work of John Eaton
+on GNU Octave, which I mainly generalized for use in other programs.
+(see section <A HREF="tutorial.html#SEC78">10. Using Fortran effectively</A>).
+<LI>
+Mark Galassi was the first person, to the best of my knowledge, who tried to
+write an Autoconf tutorial. It is thanks to his work that I was inspired to
+begin this work.
+</UL>
+<P>
+
+FIXME: <EM>I need to start keeping track of acknowledgements here</EM>
+</P><P>
+
+<A NAME="Copying"></A>
+<HR SIZE="6">
+<A NAME="SEC3"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC2"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H1> Copying </H1>
+<!--docid::SEC3::-->
+<P>
+
+This book that you are now reading is actually free. The information
+in it is freely available to anyone. The machine readable source code
+for the book is freely distributed on the internet and anyone may take
+this book and make as many copies as they like. (take a moment to
+check the copying permissions on the Copyright page). If you paid money
+for this book, what you actually paid for was the book's nice printing and
+binding, and the publisher's associated costs to produce it.
+</P><P>
+
+The following notice refers to the Autotoolset package, which includes this
+documentation, as well as the source code for utilities like <TT>`acmkdir'</TT>
+and for additional Autoconf macros. The complete <EM>GNU development tools</EM>
+involves other packages also, such as <EM>Autoconf</EM>, <EM>Automake</EM>,
+<EM>Libtool</EM>, <EM>Make</EM>, <EM>Emacs</EM>, <EM>Texinfo</EM>,
+the <EM>GNU C and C++ compilers</EM>
+and a few other accessories. These packages are free software, and you
+can obtain them from the Free Software Foundation. For details on doing so,
+please visit their web site <CODE>http://www.fsf.org/</CODE>. Although Autotoolset
+has been designed to work with the GNU build system, it is not yet an
+official part of the GNU project.
+</P><P>
+
+The Autotoolset package is also "free"; this means that everyone is free to
+use it and free to redistribute it on a free basis. The Autotoolset package is
+not in the public domain; it is copyrighted and there are restrictions
+on its distribution, but these restrictions are designed to permit
+everything that a good cooperating citizen would want to do.
+What is not allowed is to try to prevent others from further sharing
+any version of this package that they might get from you.
+</P><P>
+
+Specifically, we want to make sure that you have the right to give
+away copies of the programs that relate to <EM>Autotoolset</EM>, that you receive
+source code or else can get it if you want it, that you can change these
+programs or use pieces of them in new free programs, and that you know
+you can do these things.
+</P><P>
+
+To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of the <EM>Autotoolset</EM>-related code, you must give the recipients all
+the rights that you have. You must make sure that they, too, receive or
+can get the source code. And you must tell them their rights.
+</P><P>
+
+Also, for our own protection, we must make certain that everyone
+finds out that there is no warranty for the programs that relate to
+<EM>Autotoolset</EM>. If these programs are modified by someone else and passed
+on, we want their recipients to know that what they have is not what we
+distributed, so that any problems introduced by others will not reflect
+on our reputation.
+</P><P>
+
+The precise conditions of the licenses for the programs currently
+being distributed that relate to <EM>Autotoolset</EM> are found in the General
+Public Licenses that accompany them.
+</P><P>
+
+<A NAME="Installing GNU software"></A>
+<HR SIZE="6">
+<A NAME="SEC4"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC5"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC3"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC10"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H1> 1. Installing GNU software </H1>
+<!--docid::SEC4::-->
+<P>
+
+Free software is distributed in source code distributions. Many of these
+programs are difficult to install because they use system dependent features,
+and they require the user to edit makefiles and configuration headers.
+By contrast, the software distributed by the GNU project is
+<EM>autoconfiguring</EM>; it is possible to compile it from source code and
+install it automatically, without any tedious user intervention.
+</P><P>
+
+In this chapter we discuss how to compile and install autoconfiguring software
+written by others. In the subsequent chapters we discuss how to use the
+development tools that allow you to make your software autoconfiguring as
+well.
+</P><P>
+
+<BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC5">1.1 Installing a GNU package</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC6">1.2 The Makefile standards</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC7">1.3 Configuration options</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC8">1.4 Doing a VPATH build</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+<TR><TD ALIGN="left" VALIGN="TOP"><A HREF="tutorial.html#SEC9">1.5 Making a binary distribution</A></TD><TD> </TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+</TABLE></BLOCKQUOTE>
+<P>
+
+<A NAME="Installing a GNU package"></A>
+<HR SIZE="6">
+<A NAME="SEC5"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC6"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC10"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H2> 1.1 Installing a GNU package </H2>
+<!--docid::SEC5::-->
+<P>
+
+Autoconfiguring software is distributed with packaged source code
+distributions. These are big files with filenames of the form:
+<TABLE><tr><td> </td><td class=example><pre><VAR>package</VAR>-<VAR>version</VAR>.tar.gz
+</pre></td></tr></table>For example, the file <TT>`autoconf-2.57.tar.gz'</TT> contains
+version 2.57 of GNU Autoconf.
+We often call these
+files <EM>source distributions</EM>; sometimes we simply call them
+<EM>packages</EM>.
+</P><P>
+
+The steps for installing an autoconfiguring source code distribution are
+simple, and if the distribution is not buggy, can be carried out without
+substantial user intervention.
+<OL>
+<LI>
+First, you have to unpack the package to a directory:
+<TABLE><tr><td> </td><td class=example><pre>% gunzip foo-1.0.tar.gz
+% tar xf foo-1.0.tar
+</pre></td></tr></table>This will create the directory <TT>`foo-1.0'</TT> which contains the package's
+source code and documentation. Look for the files <TT>`README'</TT> to see
+if there's anything that you should do next. The <TT>`README'</TT> file might
+suggest that you need to install other packages before installing this one,
+or it might suggest that you have to do unusual things to install this
+package. If the source distribution conforms to the GNU coding standards,
+you will find many other documentation files like <TT>`README'</TT>.
+See section <A HREF="tutorial.html#SEC45">5.6 Maintaining the documentation files</A>, for an explanation of what
+these files mean.
+<LI>
+Configure the source code. Once upon a time that used to mean that you have
+to edit makefiles and header files. In the wonderful world of Autoconf,
+source distributions provide a <TT>`configure'</TT> script that will do that
+for you automatically. To run the script type:
+<TABLE><tr><td> </td><td class=example><pre>% cd foo-1.0
+% ./configure
+</pre></td></tr></table><LI>
+Now you can compile the source code. Type:
+<TABLE><tr><td> </td><td class=example><pre>% make
+</pre></td></tr></table>and if the program is big, you can make some coffee. After the program
+compiles, you can run its regression test-suite, if it has one,
+by typing
+<TABLE><tr><td> </td><td class=example><pre>% make check
+</pre></td></tr></table><LI>
+If everything is okey, you can install the compiled distribution with:
+<TABLE><tr><td> </td><td class=example><pre>% su
+# make install
+</pre></td></tr></table></OL>
+<P>
+
+The <TT>`make'</TT> program launches the shell commands necessary for compiling,
+testing and installing the package from source code. However, <TT>`make'</TT>
+has no knowledge of what it is really doing. It takes its orders from
+<EM>makefiles</EM>, files called <TT>`Makefile'</TT> that have to be present
+in every subdirectory of your source code directory tree. From the installer
+perspective,
+the makefiles define a set of <EM>targets</EM> that correspond to things
+that the installer wants to do. The default target is always compiling the
+source code, which is what gets invoked when you simply run <CODE>make</CODE>.
+Other targets, such as <SAMP>`install'</SAMP>, <SAMP>`check'</SAMP> need to be mentioned
+explicitly. Because <TT>`make'</TT> takes its orders from the makefile in
+the current directory, it is important to run it from the correct
+directory. See section <A HREF="tutorial.html#SEC30">4. Compiling with Makefiles</A>, for the full story behind
+<TT>`make'</TT>.
+</P><P>
+
+The <TT>`configure'</TT> program is a shell script that probes your system
+through a set of tests to
+determine things that it needs to know, and then uses the results
+to generate <TT>`Makefile'</TT> files from templates stored
+in files called <TT>`Makefile.in'</TT>. In the early days of the GNU project,
+developers used to write <TT>`configure'</TT> scripts by hand. Now, no-one
+ever does that any more. Now, <TT>`configure'</TT> scripts are automatically
+generated by GNU Autoconf from an input file <TT>`configure.in'</TT>.
+GNU Autoconf is part of the GNU build system and we first introduce
+in in <A HREF="tutorial.html#SEC39">5. The GNU build system</A>.
+</P><P>
+
+As it turns out, you don't have to write the <TT>`Makefile.in'</TT> templates
+by hand either. Instead you can use another program, GNU Automake, to
+generate <TT>`Makefile.in'</TT> templates from higher-level descriptions
+stored in files called <TT>`Makefile.am'</TT>. In these files you describe
+what is being created by your source code, and Automake computes the
+makefile targets for compiling, installing and uninstalling it. Automake
+also computes targets for compiling and running test suites, and targets
+for recursively calling <CODE>make</CODE> in subdirectories. The details about
+Automake are first introduced in <A HREF="tutorial.html#SEC50">6. Using Automake and Autoconf</A>.
+</P><P>
+
+<A NAME="The Makefile standards"></A>
+<HR SIZE="6">
+<A NAME="SEC6"></A>
+<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC5"> < </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC7"> > </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> << </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC4"> Up </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC10"> >> </A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT"> <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Top">Top</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_Contents">Contents</A>]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[Index]</TD>
+<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="tutorial.html#SEC_About"> ? </A>]</TD>
+</TR></TABLE>
+<H2> 1.2 The Makefile standards </H2>
+<!--docid::SEC6::-->
+<P>
+
+The <EM>GNU coding standards</EM> are a document that describes the requirements
+that must be satisfied by all GNU programs. These requirements are driven
+mainly by technical ocnsiderations, and they are excellent advice for
+writing good software. The <EM>makefile standards</EM>, a part of the
+GNU coding standards, require that your
+makefiles do a lot more than simply compile and install the software.
+</P><P>
+
+One requirement is <EM>cleaning targets</EM>; these targets remove the files
+that were generated while installing the package and restore the source
+distribution to a previous state. There are three cleaning targets that
+corresponds to three levels of cleaning: <CODE>clean</CODE>, <CODE>distclean</CODE>,
+<CODE>maintainer-clean</CODE>.
+<DL COMPACT>
+<DT><CODE>clean</CODE>
+<DD>Cleans up all the files that were generated by <CODE>make</CODE> and
+<CODE>make check</CODE>, but not the files that were generated by running
+<CODE>configure</CODE>. This targets cleans the build, but does not undo the
+source configuration by the configure script.
+<DT><CODE>distclean</CODE>
+<DD>Cleans up all the files generated by <CODE>make</CODE> and <CODE>make check</CODE>,
+but also cleans the files that were generated by running <CODE>configure</CODE>.
+As a result, you can not invoke any other make targets until you run
+the configure script again. This target reverts your source directory tree
+back to the state in which it was when you first unpacked it.
+<DT><CODE>maintainer-clean</CODE>
+<DD>Cleans up all the files that <CODE>distclean</CODE> cleans. However it also removes
+files that the developers have automatically generated with the GNU build
+system. Because users shouldn't need the entire GNU build system to install
+a package, these files should not be removed in the final source distribution.
+However, it is occasionally useful for the maintainer to remove and
+regenerate these files.
+</DL>
+<P>
+
+Another type of cleaning that is required is erasing the package itself from
+the installation directory; <EM>uninstalling</EM> the package. To uninstall
+the package, you must call
+<TABLE><tr><td> </td><td class=example><pre>% make uninstall
+</pre></td></tr></table>from the toplevel directory of the source distribution. This will work only
+if the source distribution is configured first. It will work best only
+if you do it from the same source distribution, with the same configuration,
+that you've used to install the package in the first place.
+</P><P>
+
+When you install GNU software, archive the source code to all the packages
+that you install in a directory like <TT>`/usr/src'</TT> or <TT>`/usr/local/src'</TT>.
+To do that, first run <CODE>make clean</CODE> on the source distribution, and then
+use a recursive copy to copy it to <TT>`/usr/src'</TT>. The presense of a
+source distribution in one of these directories should be a signal to you
+that the corresponding package is currently installed.
+</P><P>
+
+Francois Pinard came up with a cute rule for remembering what the cleaning
+targets do:
+<UL>
+<LI>
+If <CODE>configure</CODE> or <CODE>make</CODE> did it, <CODE>make distclean</CODE> undoes it.
+<LI>
+If <CODE>make</CODE> did it, <CODE>make clean</CODE> undoes it.
+<LI>
+If <CODE>make install</CODE> did it, <CODE>make uninstall</CODE> undoes it.
+<LI>
+If <EM>you</EM> did it, <CODE>make maintainer-clean</CODE> undoes it.
+</UL>
+<P>
+
+GNU standard compliant makefiles also have a target for generating <EM>tags</EM>.
+Tags are files, called <TT>`TAGS'</TT>, that are used by GNU Emacs...
[truncated message content] |
|
From: <mro...@us...> - 2007-05-14 16:45:57
|
Revision: 43
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=43&view=rev
Author: mroberto
Date: 2007-05-14 09:45:25 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Use autoreconf.
Modified Paths:
--------------
trunk/INSTALL
trunk/configure.ac
trunk/doc/tutorial/version.texi
trunk/reconf
Modified: trunk/INSTALL
===================================================================
--- trunk/INSTALL 2007-05-14 16:11:24 UTC (rev 42)
+++ trunk/INSTALL 2007-05-14 16:45:25 UTC (rev 43)
@@ -1,38 +1,43 @@
-Generating RPMS
-===============
+Installation Instructions
+*************************
- If you started with the tar ball, just do
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
- rpmbuild -tb autotools-X.Y.Z.tar.gz
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
-and provided you have the rights to write in the right places, you
-will have the binary rpm of the package.
-
-
Basic Installation
==================
- These are generic installation instructions.
+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, 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 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:
@@ -65,20 +70,22 @@
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.
-Or on systems that have the `env' program, you can do it like this:
- env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+ 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
+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
@@ -86,28 +93,28 @@
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.
+ 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' will install the package's files in
+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'.
+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.
+give `configure' the option `--exec-prefix=PREFIX', the package will
+use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will 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.
@@ -118,7 +125,7 @@
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
@@ -133,48 +140,86 @@
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 can also
+ If you are _building_ compiler tools for cross-compiling, you should
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.
+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'.
+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). 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'
@@ -186,8 +231,6 @@
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.
Modified: trunk/configure.ac
===================================================================
--- trunk/configure.ac 2007-05-14 16:11:24 UTC (rev 42)
+++ trunk/configure.ac 2007-05-14 16:45:25 UTC (rev 43)
@@ -16,10 +16,11 @@
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-AC_INIT([GNU autotoolset], [0.11.5],
+AC_INIT([GNU autotoolset], [0.11.6],
[Marcelo Roberto Jimenez <mro...@ce...>],
[autotoolset])
AC_CONFIG_SRCDIR(src/Makefile.am)
+AC_CONFIG_AUX_DIR(config.aux)
AM_INIT_AUTOMAKE([dist-bzip2])
# C compiler stuff
Modified: trunk/doc/tutorial/version.texi
===================================================================
--- trunk/doc/tutorial/version.texi 2007-05-14 16:11:24 UTC (rev 42)
+++ trunk/doc/tutorial/version.texi 2007-05-14 16:45:25 UTC (rev 43)
@@ -1,4 +1,4 @@
@set UPDATED 14 May 2007
@set UPDATED-MONTH May 2007
-@set EDITION 0.11.5
-@set VERSION 0.11.5
+@set EDITION 0.11.6
+@set VERSION 0.11.6
Modified: trunk/reconf
===================================================================
--- trunk/reconf 2007-05-14 16:11:24 UTC (rev 42)
+++ trunk/reconf 2007-05-14 16:45:25 UTC (rev 43)
@@ -1,3 +1,4 @@
+#!/bin/sh
# Copyright (C) 1988 Eleftherios Gkioulekas <lf...@am...>
#
# This program is free software; you can redistribute it and/or modify
@@ -14,27 +15,15 @@
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-#!/bin/sh
-rm -f config.cache
-rm -f acconfig.h
+rm -fr autom4te.cache
-## If using libtool
-#echo "libtoolize..."
-#libtoolize --force
+# Equivalent to
+# aclocal
+# autoheader
+# automake --add-missing --copy
+# autoconf
+autoreconf --verbose --force --install -Wall -Wno-obsolete $* || exit 1
-echo "- aclocal..."
-aclocal -I m4
+echo "Now run ./configure and then make."
+exit 0
-echo "- autoconf..."
-autoconf
-
-## If using the c header
-#echo "- autoheader..."
-#autoheader
-
-echo "- automake..."
-#automake -a -v
-automake -a
-
-echo "- ready!"
-exit
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-14 16:12:23
|
Revision: 41
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=41&view=rev
Author: mroberto
Date: 2007-05-14 09:10:39 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Removing bad file.
Removed Paths:
-------------
trunk/src/acmkdir/fortran.tar.gz
Deleted: trunk/src/acmkdir/fortran.tar.gz
===================================================================
--- trunk/src/acmkdir/fortran.tar.gz 2007-05-14 15:49:01 UTC (rev 40)
+++ trunk/src/acmkdir/fortran.tar.gz 2007-05-14 16:10:39 UTC (rev 41)
@@ -1,2763 +0,0 @@
- \x8B\xD4G\xAA5 |
|
From: <mro...@us...> - 2007-05-14 16:12:23
|
Revision: 42
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=42&view=rev
Author: mroberto
Date: 2007-05-14 09:11:24 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Readding file.
Added Paths:
-----------
trunk/src/acmkdir/fortran.tar.gz
Added: trunk/src/acmkdir/fortran.tar.gz
===================================================================
(Binary files differ)
Property changes on: trunk/src/acmkdir/fortran.tar.gz
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-14 15:49:02
|
Revision: 40
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=40&view=rev
Author: mroberto
Date: 2007-05-14 08:49:01 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Adding svnignore and setting svn:ignore property.
Added Paths:
-----------
trunk/svnignore
Property Changed:
----------------
trunk/
trunk/debian/
trunk/doc/
trunk/doc/gnits/
trunk/doc/html/
trunk/doc/manual/
trunk/doc/notes/
trunk/doc/texinfo/
trunk/doc/tutorial/
trunk/lib/
trunk/m4/
trunk/misc/
trunk/src/
trunk/src/acconfig/
trunk/src/acmkdir/
trunk/src/acmkdir/python/
trunk/src/emacs/
trunk/src/gpl/
trunk/src/mkconfig/
trunk/src/txtc/
Property changes on: trunk
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/debian
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/gnits
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/html
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/manual
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/notes
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/texinfo
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/doc/tutorial
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/lib
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/m4
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/misc
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/acconfig
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/acmkdir
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/acmkdir/python
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/emacs
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/gpl
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/mkconfig
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Property changes on: trunk/src/txtc
___________________________________________________________________
Name: svn:ignore
+ Makefile
Makefile.in
configure
*.o
*.in
Added: trunk/svnignore
===================================================================
--- trunk/svnignore (rev 0)
+++ trunk/svnignore 2007-05-14 15:49:01 UTC (rev 40)
@@ -0,0 +1,6 @@
+Makefile
+Makefile.in
+configure
+*.o
+*.in
+
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <mro...@us...> - 2007-05-14 14:34:28
|
Revision: 39
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=39&view=rev
Author: mroberto
Date: 2007-05-14 07:34:25 -0700 (Mon, 14 May 2007)
Log Message:
-----------
Removed configure from version control.
Fix for cross reference.
Modified Paths:
--------------
trunk/doc/tutorial/tutorial.texi
trunk/doc/tutorial/version.texi
Removed Paths:
-------------
trunk/configure
Deleted: trunk/configure
===================================================================
--- trunk/configure 2007-05-14 01:06:09 UTC (rev 38)
+++ trunk/configure 2007-05-14 14:34:25 UTC (rev 39)
@@ -1,6564 +0,0 @@
-#! /bin/sh
-# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.60 for GNU autotoolset 0.11.5.
-#
-# Report bugs to <Marcelo Roberto Jimenez <mro...@ce...>>.
-#
-# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
-# 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
-# This configure script is free software; the Free Software Foundation
-# gives unlimited permission to copy, distribute and modify it.
-## --------------------- ##
-## M4sh Initialization. ##
-## --------------------- ##
-
-# Be Bourne compatible
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
-fi
-BIN_SH=xpg4; export BIN_SH # for Tru64
-DUALCASE=1; export DUALCASE # for MKS sh
-
-
-# PATH needs CR
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- echo "#! /bin/sh" >conf$$.sh
- echo "exit 0" >>conf$$.sh
- chmod +x conf$$.sh
- if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
- PATH_SEPARATOR=';'
- else
- PATH_SEPARATOR=:
- fi
- rm -f conf$$.sh
-fi
-
-# Support unset when possible.
-if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
- as_unset=unset
-else
- as_unset=false
-fi
-
-
-# IFS
-# We need space, tab and new line, in precisely that order. Quoting is
-# there to prevent editors from complaining about space-tab.
-# (If _AS_PATH_WALK were called with IFS unset, it would disable word
-# splitting by setting IFS to empty value.)
-as_nl='
-'
-IFS=" "" $as_nl"
-
-# Find who we are. Look in the path if we contain no directory separator.
-case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
-IFS=$as_save_IFS
-
- ;;
-esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
-# in which case we are not to be found in the path.
-if test "x$as_myself" = x; then
- as_myself=$0
-fi
-if test ! -f "$as_myself"; then
- echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
- { (exit 1); exit 1; }
-fi
-
-# Work around bugs in pre-3.0 UWIN ksh.
-for as_var in ENV MAIL MAILPATH
-do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
-done
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-for as_var in \
- LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \
- LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \
- LC_TELEPHONE LC_TIME
-do
- if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then
- eval $as_var=C; export $as_var
- else
- ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
- fi
-done
-
-# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-
-# Name of the executable.
-as_me=`$as_basename -- "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{
- s//\1/
- q
- }
- /^X\/\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\/\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
-
-# CDPATH.
-$as_unset CDPATH
-
-
-if test "x$CONFIG_SHELL" = x; then
- if (eval ":") 2>/dev/null; then
- as_have_required=yes
-else
- as_have_required=no
-fi
-
- if test $as_have_required = yes && (eval ":
-(as_func_return () {
- (exit \$1)
-}
-as_func_success () {
- as_func_return 0
-}
-as_func_failure () {
- as_func_return 1
-}
-as_func_ret_success () {
- return 0
-}
-as_func_ret_failure () {
- return 1
-}
-
-exitcode=0
-if as_func_success; then
- :
-else
- exitcode=1
- echo as_func_success failed.
-fi
-
-if as_func_failure; then
- exitcode=1
- echo as_func_failure succeeded.
-fi
-
-if as_func_ret_success; then
- :
-else
- exitcode=1
- echo as_func_ret_success failed.
-fi
-
-if as_func_ret_failure; then
- exitcode=1
- echo as_func_ret_failure succeeded.
-fi
-
-if ( set x; as_func_ret_success y && test x = \"\$1\" ); then
- :
-else
- exitcode=1
- echo positional parameters were not saved.
-fi
-
-test \$exitcode = 0) || { (exit 1); exit 1; }
-
-(
- as_lineno_1=\$LINENO
- as_lineno_2=\$LINENO
- test \"x\$as_lineno_1\" != \"x\$as_lineno_2\" &&
- test \"x\`expr \$as_lineno_1 + 1\`\" = \"x\$as_lineno_2\") || { (exit 1); exit 1; }
-") 2> /dev/null; then
- :
-else
- as_candidate_shells=
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in /usr/bin/posix$PATH_SEPARATOR/bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- case $as_dir in
- /*)
- for as_base in sh bash ksh sh5; do
- as_candidate_shells="$as_candidate_shells $as_dir/$as_base"
- done;;
- esac
-done
-IFS=$as_save_IFS
-
-
- for as_shell in $as_candidate_shells $SHELL; do
- # Try only shells that exist, to save several forks.
- if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
- { ("$as_shell") 2> /dev/null <<\_ASEOF
-# Be Bourne compatible
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
-fi
-BIN_SH=xpg4; export BIN_SH # for Tru64
-DUALCASE=1; export DUALCASE # for MKS sh
-
-:
-_ASEOF
-}; then
- CONFIG_SHELL=$as_shell
- as_have_required=yes
- if { "$as_shell" 2> /dev/null <<\_ASEOF
-# Be Bourne compatible
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
-fi
-BIN_SH=xpg4; export BIN_SH # for Tru64
-DUALCASE=1; export DUALCASE # for MKS sh
-
-:
-(as_func_return () {
- (exit $1)
-}
-as_func_success () {
- as_func_return 0
-}
-as_func_failure () {
- as_func_return 1
-}
-as_func_ret_success () {
- return 0
-}
-as_func_ret_failure () {
- return 1
-}
-
-exitcode=0
-if as_func_success; then
- :
-else
- exitcode=1
- echo as_func_success failed.
-fi
-
-if as_func_failure; then
- exitcode=1
- echo as_func_failure succeeded.
-fi
-
-if as_func_ret_success; then
- :
-else
- exitcode=1
- echo as_func_ret_success failed.
-fi
-
-if as_func_ret_failure; then
- exitcode=1
- echo as_func_ret_failure succeeded.
-fi
-
-if ( set x; as_func_ret_success y && test x = "$1" ); then
- :
-else
- exitcode=1
- echo positional parameters were not saved.
-fi
-
-test $exitcode = 0) || { (exit 1); exit 1; }
-
-(
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2") || { (exit 1); exit 1; }
-
-_ASEOF
-}; then
- break
-fi
-
-fi
-
- done
-
- if test "x$CONFIG_SHELL" != x; then
- for as_var in BASH_ENV ENV
- do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
- done
- export CONFIG_SHELL
- exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"}
-fi
-
-
- if test $as_have_required = no; then
- echo This script requires a shell more modern than all the
- echo shells that I found on your system. Please install a
- echo modern shell, or manually run the script under such a
- echo shell if you do have one.
- { (exit 1); exit 1; }
-fi
-
-
-fi
-
-fi
-
-
-
-(eval "as_func_return () {
- (exit \$1)
-}
-as_func_success () {
- as_func_return 0
-}
-as_func_failure () {
- as_func_return 1
-}
-as_func_ret_success () {
- return 0
-}
-as_func_ret_failure () {
- return 1
-}
-
-exitcode=0
-if as_func_success; then
- :
-else
- exitcode=1
- echo as_func_success failed.
-fi
-
-if as_func_failure; then
- exitcode=1
- echo as_func_failure succeeded.
-fi
-
-if as_func_ret_success; then
- :
-else
- exitcode=1
- echo as_func_ret_success failed.
-fi
-
-if as_func_ret_failure; then
- exitcode=1
- echo as_func_ret_failure succeeded.
-fi
-
-if ( set x; as_func_ret_success y && test x = \"\$1\" ); then
- :
-else
- exitcode=1
- echo positional parameters were not saved.
-fi
-
-test \$exitcode = 0") || {
- echo No shell found that supports shell functions.
- echo Please tell aut...@gn... about your system,
- echo including any error possibly output before this
- echo message
-}
-
-
-
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2" || {
-
- # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
- # uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line after each line using $LINENO; the second 'sed'
- # does the real work. The second script uses 'N' to pair each
- # line-number line with the line containing $LINENO, and appends
- # trailing '-' during substitution so that $LINENO is not a special
- # case at line end.
- # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # scripts with optimization help from Paolo Bonzini. Blame Lee
- # E. McMahon (1931-1989) for sed's syntax. :-)
- sed -n '
- p
- /[$]LINENO/=
- ' <$as_myself |
- sed '
- s/[$]LINENO.*/&-/
- t lineno
- b
- :lineno
- N
- :loop
- s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
- t loop
- s/-\n.*//
- ' >$as_me.lineno &&
- chmod +x "$as_me.lineno" ||
- { echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
- { (exit 1); exit 1; }; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensitive to this).
- . "./$as_me.lineno"
- # Exit status is that of the last command.
- exit
-}
-
-
-if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
- as_dirname=dirname
-else
- as_dirname=false
-fi
-
-ECHO_C= ECHO_N= ECHO_T=
-case `echo -n x` in
--n*)
- case `echo 'x\c'` in
- *c*) ECHO_T=' ';; # ECHO_T is single tab character.
- *) ECHO_C='\c';;
- esac;;
-*)
- ECHO_N='-n';;
-esac
-
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-rm -f conf$$ conf$$.exe conf$$.file
-if test -d conf$$.dir; then
- rm -f conf$$.dir/conf$$.file
-else
- rm -f conf$$.dir
- mkdir conf$$.dir
-fi
-echo >conf$$.file
-if ln -s conf$$.file conf$$ 2>/dev/null; then
- as_ln_s='ln -s'
- # ... but there are two gotchas:
- # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
- # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
- # In both cases, we have to default to `cp -p'.
- ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
- as_ln_s='cp -p'
-elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
-rmdir conf$$.dir 2>/dev/null
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p=:
-else
- test -d ./-p && rmdir ./-p
- as_mkdir_p=false
-fi
-
-# Find out whether ``test -x'' works. Don't use a zero-byte file, as
-# systems may use methods other than mode bits to determine executability.
-cat >conf$$.file <<_ASEOF
-#! /bin/sh
-exit 0
-_ASEOF
-chmod +x conf$$.file
-if test -x conf$$.file >/dev/null 2>&1; then
- as_executable_p="test -x"
-else
- as_executable_p=:
-fi
-rm -f conf$$.file
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-
-
-
-exec 7<&0 </dev/null 6>&1
-
-# Name of the host.
-# hostname on some systems (SVR3.2, Linux) returns a bogus exit status,
-# so uname gets run too.
-ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
-
-#
-# Initializations.
-#
-ac_default_prefix=/usr/local
-ac_clean_files=
-ac_config_libobj_dir=.
-LIBOBJS=
-cross_compiling=no
-subdirs=
-MFLAGS=
-MAKEFLAGS=
-SHELL=${CONFIG_SHELL-/bin/sh}
-
-# Identity of this package.
-PACKAGE_NAME='GNU autotoolset'
-PACKAGE_TARNAME='autotoolset'
-PACKAGE_VERSION='0.11.5'
-PACKAGE_STRING='GNU autotoolset 0.11.5'
-PACKAGE_BUGREPORT='Marcelo Roberto Jimenez <mro...@ce...>'
-
-ac_unique_file="src/Makefile.am"
-# Factoring default headers for most tests.
-ac_includes_default="\
-#include <stdio.h>
-#if HAVE_SYS_TYPES_H
-# include <sys/types.h>
-#endif
-#if HAVE_SYS_STAT_H
-# include <sys/stat.h>
-#endif
-#if STDC_HEADERS
-# include <stdlib.h>
-# include <stddef.h>
-#else
-# if HAVE_STDLIB_H
-# include <stdlib.h>
-# endif
-#endif
-#if HAVE_STRING_H
-# if !STDC_HEADERS && HAVE_MEMORY_H
-# include <memory.h>
-# endif
-# include <string.h>
-#endif
-#if HAVE_STRINGS_H
-# include <strings.h>
-#endif
-#if HAVE_INTTYPES_H
-# include <inttypes.h>
-#endif
-#if HAVE_STDINT_H
-# include <stdint.h>
-#endif
-#if HAVE_UNISTD_H
-# include <unistd.h>
-#endif"
-
-ac_subst_vars='SHELL
-PATH_SEPARATOR
-PACKAGE_NAME
-PACKAGE_TARNAME
-PACKAGE_VERSION
-PACKAGE_STRING
-PACKAGE_BUGREPORT
-exec_prefix
-prefix
-program_transform_name
-bindir
-sbindir
-libexecdir
-datarootdir
-datadir
-sysconfdir
-sharedstatedir
-localstatedir
-includedir
-oldincludedir
-docdir
-infodir
-htmldir
-dvidir
-pdfdir
-psdir
-libdir
-localedir
-mandir
-DEFS
-ECHO_C
-ECHO_N
-ECHO_T
-LIBS
-build_alias
-host_alias
-target_alias
-INSTALL_PROGRAM
-INSTALL_SCRIPT
-INSTALL_DATA
-CYGPATH_W
-PACKAGE
-VERSION
-ACLOCAL
-AUTOCONF
-AUTOMAKE
-AUTOHEADER
-MAKEINFO
-install_sh
-STRIP
-INSTALL_STRIP_PROGRAM
-mkdir_p
-AWK
-SET_MAKE
-am__leading_dot
-AMTAR
-am__tar
-am__untar
-CC
-CFLAGS
-LDFLAGS
-CPPFLAGS
-ac_ct_CC
-EXEEXT
-OBJEXT
-DEPDIR
-am__include
-am__quote
-AMDEP_TRUE
-AMDEP_FALSE
-AMDEPBACKSLASH
-CCDEPMODE
-am__fastdepCC_TRUE
-am__fastdepCC_FALSE
-LN_S
-RANLIB
-BASH
-TXTC
-PERL
-SHAR
-ZCAT
-EMACS
-EMACSLOADPATH
-lispdir
-ALLOCA
-CPP
-GREP
-EGREP
-LIBOBJS
-LTLIBOBJS'
-ac_subst_files=''
- ac_precious_vars='build_alias
-host_alias
-target_alias
-CC
-CFLAGS
-LDFLAGS
-CPPFLAGS
-EMACS
-EMACSLOADPATH
-CPP'
-
-
-# Initialize some variables set by options.
-ac_init_help=
-ac_init_version=false
-# The variables have the same names as the options, with
-# dashes changed to underlines.
-cache_file=/dev/null
-exec_prefix=NONE
-no_create=
-no_recursion=
-prefix=NONE
-program_prefix=NONE
-program_suffix=NONE
-program_transform_name=s,x,x,
-silent=
-site=
-srcdir=
-verbose=
-x_includes=NONE
-x_libraries=NONE
-
-# Installation directory options.
-# These are left unexpanded so users can "make install exec_prefix=/foo"
-# and all the variables that are supposed to be based on exec_prefix
-# by default will actually change.
-# Use braces instead of parens because sh, perl, etc. also accept them.
-# (The list follows the same order as the GNU Coding Standards.)
-bindir='${exec_prefix}/bin'
-sbindir='${exec_prefix}/sbin'
-libexecdir='${exec_prefix}/libexec'
-datarootdir='${prefix}/share'
-datadir='${datarootdir}'
-sysconfdir='${prefix}/etc'
-sharedstatedir='${prefix}/com'
-localstatedir='${prefix}/var'
-includedir='${prefix}/include'
-oldincludedir='/usr/include'
-docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
-infodir='${datarootdir}/info'
-htmldir='${docdir}'
-dvidir='${docdir}'
-pdfdir='${docdir}'
-psdir='${docdir}'
-libdir='${exec_prefix}/lib'
-localedir='${datarootdir}/locale'
-mandir='${datarootdir}/man'
-
-ac_prev=
-ac_dashdash=
-for ac_option
-do
- # If the previous option needs an argument, assign it.
- if test -n "$ac_prev"; then
- eval $ac_prev=\$ac_option
- ac_prev=
- continue
- fi
-
- case $ac_option in
- *=*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
- *) ac_optarg=yes ;;
- esac
-
- # Accept the important Cygnus configure options, so we can diagnose typos.
-
- case $ac_dashdash$ac_option in
- --)
- ac_dashdash=yes ;;
-
- -bindir | --bindir | --bindi | --bind | --bin | --bi)
- ac_prev=bindir ;;
- -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
- bindir=$ac_optarg ;;
-
- -build | --build | --buil | --bui | --bu)
- ac_prev=build_alias ;;
- -build=* | --build=* | --buil=* | --bui=* | --bu=*)
- build_alias=$ac_optarg ;;
-
- -cache-file | --cache-file | --cache-fil | --cache-fi \
- | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
- ac_prev=cache_file ;;
- -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
- | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
- cache_file=$ac_optarg ;;
-
- --config-cache | -C)
- cache_file=config.cache ;;
-
- -datadir | --datadir | --datadi | --datad)
- ac_prev=datadir ;;
- -datadir=* | --datadir=* | --datadi=* | --datad=*)
- datadir=$ac_optarg ;;
-
- -datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
- | --dataroo | --dataro | --datar)
- ac_prev=datarootdir ;;
- -datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
- | --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
- datarootdir=$ac_optarg ;;
-
- -disable-* | --disable-*)
- ac_feature=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid feature name: $ac_feature" >&2
- { (exit 1); exit 1; }; }
- ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- eval enable_$ac_feature=no ;;
-
- -docdir | --docdir | --docdi | --doc | --do)
- ac_prev=docdir ;;
- -docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
- docdir=$ac_optarg ;;
-
- -dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
- ac_prev=dvidir ;;
- -dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
- dvidir=$ac_optarg ;;
-
- -enable-* | --enable-*)
- ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid feature name: $ac_feature" >&2
- { (exit 1); exit 1; }; }
- ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- eval enable_$ac_feature=\$ac_optarg ;;
-
- -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
- | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
- | --exec | --exe | --ex)
- ac_prev=exec_prefix ;;
- -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
- | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
- | --exec=* | --exe=* | --ex=*)
- exec_prefix=$ac_optarg ;;
-
- -gas | --gas | --ga | --g)
- # Obsolete; use --with-gas.
- with_gas=yes ;;
-
- -help | --help | --hel | --he | -h)
- ac_init_help=long ;;
- -help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
- ac_init_help=recursive ;;
- -help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
- ac_init_help=short ;;
-
- -host | --host | --hos | --ho)
- ac_prev=host_alias ;;
- -host=* | --host=* | --hos=* | --ho=*)
- host_alias=$ac_optarg ;;
-
- -htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
- ac_prev=htmldir ;;
- -htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
- | --ht=*)
- htmldir=$ac_optarg ;;
-
- -includedir | --includedir | --includedi | --included | --include \
- | --includ | --inclu | --incl | --inc)
- ac_prev=includedir ;;
- -includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
- | --includ=* | --inclu=* | --incl=* | --inc=*)
- includedir=$ac_optarg ;;
-
- -infodir | --infodir | --infodi | --infod | --info | --inf)
- ac_prev=infodir ;;
- -infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
- infodir=$ac_optarg ;;
-
- -libdir | --libdir | --libdi | --libd)
- ac_prev=libdir ;;
- -libdir=* | --libdir=* | --libdi=* | --libd=*)
- libdir=$ac_optarg ;;
-
- -libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
- | --libexe | --libex | --libe)
- ac_prev=libexecdir ;;
- -libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
- | --libexe=* | --libex=* | --libe=*)
- libexecdir=$ac_optarg ;;
-
- -localedir | --localedir | --localedi | --localed | --locale)
- ac_prev=localedir ;;
- -localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
- localedir=$ac_optarg ;;
-
- -localstatedir | --localstatedir | --localstatedi | --localstated \
- | --localstate | --localstat | --localsta | --localst | --locals)
- ac_prev=localstatedir ;;
- -localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
- | --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
- localstatedir=$ac_optarg ;;
-
- -mandir | --mandir | --mandi | --mand | --man | --ma | --m)
- ac_prev=mandir ;;
- -mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
- mandir=$ac_optarg ;;
-
- -nfp | --nfp | --nf)
- # Obsolete; use --without-fp.
- with_fp=no ;;
-
- -no-create | --no-create | --no-creat | --no-crea | --no-cre \
- | --no-cr | --no-c | -n)
- no_create=yes ;;
-
- -no-recursion | --no-recursion | --no-recursio | --no-recursi \
- | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
- no_recursion=yes ;;
-
- -oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
- | --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
- | --oldin | --oldi | --old | --ol | --o)
- ac_prev=oldincludedir ;;
- -oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
- | --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
- | --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
- oldincludedir=$ac_optarg ;;
-
- -prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
- ac_prev=prefix ;;
- -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
- prefix=$ac_optarg ;;
-
- -program-prefix | --program-prefix | --program-prefi | --program-pref \
- | --program-pre | --program-pr | --program-p)
- ac_prev=program_prefix ;;
- -program-prefix=* | --program-prefix=* | --program-prefi=* \
- | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
- program_prefix=$ac_optarg ;;
-
- -program-suffix | --program-suffix | --program-suffi | --program-suff \
- | --program-suf | --program-su | --program-s)
- ac_prev=program_suffix ;;
- -program-suffix=* | --program-suffix=* | --program-suffi=* \
- | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
- program_suffix=$ac_optarg ;;
-
- -program-transform-name | --program-transform-name \
- | --program-transform-nam | --program-transform-na \
- | --program-transform-n | --program-transform- \
- | --program-transform | --program-transfor \
- | --program-transfo | --program-transf \
- | --program-trans | --program-tran \
- | --progr-tra | --program-tr | --program-t)
- ac_prev=program_transform_name ;;
- -program-transform-name=* | --program-transform-name=* \
- | --program-transform-nam=* | --program-transform-na=* \
- | --program-transform-n=* | --program-transform-=* \
- | --program-transform=* | --program-transfor=* \
- | --program-transfo=* | --program-transf=* \
- | --program-trans=* | --program-tran=* \
- | --progr-tra=* | --program-tr=* | --program-t=*)
- program_transform_name=$ac_optarg ;;
-
- -pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
- ac_prev=pdfdir ;;
- -pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
- pdfdir=$ac_optarg ;;
-
- -psdir | --psdir | --psdi | --psd | --ps)
- ac_prev=psdir ;;
- -psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
- psdir=$ac_optarg ;;
-
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil)
- silent=yes ;;
-
- -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
- ac_prev=sbindir ;;
- -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
- | --sbi=* | --sb=*)
- sbindir=$ac_optarg ;;
-
- -sharedstatedir | --sharedstatedir | --sharedstatedi \
- | --sharedstated | --sharedstate | --sharedstat | --sharedsta \
- | --sharedst | --shareds | --shared | --share | --shar \
- | --sha | --sh)
- ac_prev=sharedstatedir ;;
- -sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
- | --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
- | --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
- | --sha=* | --sh=*)
- sharedstatedir=$ac_optarg ;;
-
- -site | --site | --sit)
- ac_prev=site ;;
- -site=* | --site=* | --sit=*)
- site=$ac_optarg ;;
-
- -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
- ac_prev=srcdir ;;
- -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
- srcdir=$ac_optarg ;;
-
- -sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
- | --syscon | --sysco | --sysc | --sys | --sy)
- ac_prev=sysconfdir ;;
- -sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
- | --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
- sysconfdir=$ac_optarg ;;
-
- -target | --target | --targe | --targ | --tar | --ta | --t)
- ac_prev=target_alias ;;
- -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
- target_alias=$ac_optarg ;;
-
- -v | -verbose | --verbose | --verbos | --verbo | --verb)
- verbose=yes ;;
-
- -version | --version | --versio | --versi | --vers | -V)
- ac_init_version=: ;;
-
- -with-* | --with-*)
- ac_package=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid package name: $ac_package" >&2
- { (exit 1); exit 1; }; }
- ac_package=`echo $ac_package| sed 's/-/_/g'`
- eval with_$ac_package=\$ac_optarg ;;
-
- -without-* | --without-*)
- ac_package=`expr "x$ac_option" : 'x-*without-\(.*\)'`
- # Reject names that are not valid shell variable names.
- expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid package name: $ac_package" >&2
- { (exit 1); exit 1; }; }
- ac_package=`echo $ac_package | sed 's/-/_/g'`
- eval with_$ac_package=no ;;
-
- --x)
- # Obsolete; use --with-x.
- with_x=yes ;;
-
- -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
- | --x-incl | --x-inc | --x-in | --x-i)
- ac_prev=x_includes ;;
- -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
- | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
- x_includes=$ac_optarg ;;
-
- -x-libraries | --x-libraries | --x-librarie | --x-librari \
- | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
- ac_prev=x_libraries ;;
- -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
- | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
- x_libraries=$ac_optarg ;;
-
- -*) { echo "$as_me: error: unrecognized option: $ac_option
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; }
- ;;
-
- *=*)
- ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
- # Reject names that are not valid shell variable names.
- expr "x$ac_envvar" : ".*[^_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid variable name: $ac_envvar" >&2
- { (exit 1); exit 1; }; }
- eval $ac_envvar=\$ac_optarg
- export $ac_envvar ;;
-
- *)
- # FIXME: should be removed in autoconf 3.0.
- echo "$as_me: WARNING: you should use --build, --host, --target" >&2
- expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
- echo "$as_me: WARNING: invalid host type: $ac_option" >&2
- : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}
- ;;
-
- esac
-done
-
-if test -n "$ac_prev"; then
- ac_option=--`echo $ac_prev | sed 's/_/-/g'`
- { echo "$as_me: error: missing argument to $ac_option" >&2
- { (exit 1); exit 1; }; }
-fi
-
-# Be sure to have absolute directory names.
-for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
- datadir sysconfdir sharedstatedir localstatedir includedir \
- oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
- libdir localedir mandir
-do
- eval ac_val=\$$ac_var
- case $ac_val in
- [\\/$]* | ?:[\\/]* ) continue;;
- NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
- esac
- { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
- { (exit 1); exit 1; }; }
-done
-
-# There might be people who depend on the old broken behavior: `$host'
-# used to hold the argument of --host etc.
-# FIXME: To remove some day.
-build=$build_alias
-host=$host_alias
-target=$target_alias
-
-# FIXME: To remove some day.
-if test "x$host_alias" != x; then
- if test "x$build_alias" = x; then
- cross_compiling=maybe
- echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host.
- If a cross compiler is detected then cross compile mode will be used." >&2
- elif test "x$build_alias" != "x$host_alias"; then
- cross_compiling=yes
- fi
-fi
-
-ac_tool_prefix=
-test -n "$host_alias" && ac_tool_prefix=$host_alias-
-
-test "$silent" = yes && exec 6>/dev/null
-
-
-ac_pwd=`pwd` && test -n "$ac_pwd" &&
-ac_ls_di=`ls -di .` &&
-ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
- { echo "$as_me: error: Working directory cannot be determined" >&2
- { (exit 1); exit 1; }; }
-test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
- { echo "$as_me: error: pwd does not report name of working directory" >&2
- { (exit 1); exit 1; }; }
-
-
-# Find the source files, if location was not specified.
-if test -z "$srcdir"; then
- ac_srcdir_defaulted=yes
- # Try the directory containing this script, then the parent directory.
- ac_confdir=`$as_dirname -- "$0" ||
-$as_expr X"$0" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$0" : 'X\(//\)[^/]' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-echo X"$0" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- srcdir=$ac_confdir
- if test ! -r "$srcdir/$ac_unique_file"; then
- srcdir=..
- fi
-else
- ac_srcdir_defaulted=no
-fi
-if test ! -r "$srcdir/$ac_unique_file"; then
- test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
- { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2
- { (exit 1); exit 1; }; }
-fi
-ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
-ac_abs_confdir=`(
- cd "$srcdir" && test -r "./$ac_unique_file" || { echo "$as_me: error: $ac_msg" >&2
- { (exit 1); exit 1; }; }
- pwd)`
-# When building in place, set srcdir=.
-if test "$ac_abs_confdir" = "$ac_pwd"; then
- srcdir=.
-fi
-# Remove unnecessary trailing slashes from srcdir.
-# Double slashes in file names in object file debugging info
-# mess up M-x gdb in Emacs.
-case $srcdir in
-*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
-esac
-for ac_var in $ac_precious_vars; do
- eval ac_env_${ac_var}_set=\${${ac_var}+set}
- eval ac_env_${ac_var}_value=\$${ac_var}
- eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
- eval ac_cv_env_${ac_var}_value=\$${ac_var}
-done
-
-#
-# Report the --help message.
-#
-if test "$ac_init_help" = "long"; then
- # Omit some internal or obsolete options to make the list less imposing.
- # This message is too long to be a string in the A/UX 3.1 sh.
- cat <<_ACEOF
-\`configure' configures GNU autotoolset 0.11.5 to adapt to many kinds of systems.
-
-Usage: $0 [OPTION]... [VAR=VALUE]...
-
-To assign environment variables (e.g., CC, CFLAGS...), specify them as
-VAR=VALUE. See below for descriptions of some of the useful variables.
-
-Defaults for the options are specified in brackets.
-
-Configuration:
- -h, --help display this help and exit
- --help=short display options specific to this package
- --help=recursive display the short help of all the included packages
- -V, --version display version information and exit
- -q, --quiet, --silent do not print \`checking...' messages
- --cache-file=FILE cache test results in FILE [disabled]
- -C, --config-cache alias for \`--cache-file=config.cache'
- -n, --no-create do not create output files
- --srcdir=DIR find the sources in DIR [configure dir or \`..']
-
-Installation directories:
- --prefix=PREFIX install architecture-independent files in PREFIX
- [$ac_default_prefix]
- --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
- [PREFIX]
-
-By default, \`make install' will install all the files in
-\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
-an installation prefix other than \`$ac_default_prefix' using \`--prefix',
-for instance \`--prefix=\$HOME'.
-
-For better control, use the options below.
-
-Fine tuning of the installation directories:
- --bindir=DIR user executables [EPREFIX/bin]
- --sbindir=DIR system admin executables [EPREFIX/sbin]
- --libexecdir=DIR program executables [EPREFIX/libexec]
- --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
- --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
- --localstatedir=DIR modifiable single-machine data [PREFIX/var]
- --libdir=DIR object code libraries [EPREFIX/lib]
- --includedir=DIR C header files [PREFIX/include]
- --oldincludedir=DIR C header files for non-gcc [/usr/include]
- --datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
- --datadir=DIR read-only architecture-independent data [DATAROOTDIR]
- --infodir=DIR info documentation [DATAROOTDIR/info]
- --localedir=DIR locale-dependent data [DATAROOTDIR/locale]
- --mandir=DIR man documentation [DATAROOTDIR/man]
- --docdir=DIR documentation root [DATAROOTDIR/doc/autotoolset]
- --htmldir=DIR html documentation [DOCDIR]
- --dvidir=DIR dvi documentation [DOCDIR]
- --pdfdir=DIR pdf documentation [DOCDIR]
- --psdir=DIR ps documentation [DOCDIR]
-_ACEOF
-
- cat <<\_ACEOF
-
-Program names:
- --program-prefix=PREFIX prepend PREFIX to installed program names
- --program-suffix=SUFFIX append SUFFIX to installed program names
- --program-transform-name=PROGRAM run sed PROGRAM on installed program names
-_ACEOF
-fi
-
-if test -n "$ac_init_help"; then
- case $ac_init_help in
- short | recursive ) echo "Configuration of GNU autotoolset 0.11.5:";;
- esac
- cat <<\_ACEOF
-
-Optional Features:
- --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
- --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
- --disable-dependency-tracking speeds up one-time build
- --enable-dependency-tracking do not reject slow dependency extractors
-
-Optional Packages:
- --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
- --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
- --with-lispdir override the default lisp directory
-
-Some influential environment variables:
- CC C compiler command
- CFLAGS C compiler flags
- LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
- nonstandard directory <lib dir>
- CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
- you have headers in a nonstandard directory <include dir>
- EMACS the Emacs editor command
- EMACSLOADPATH
- the Emacs library search path
- CPP C preprocessor
-
-Use these variables to override the choices made by `configure' or to help
-it to find libraries and programs with nonstandard names/locations.
-
-Report bugs to <Marcelo Roberto Jimenez <mro...@ce...>>.
-_ACEOF
-ac_status=$?
-fi
-
-if test "$ac_init_help" = "recursive"; then
- # If there are subdirs, report their specific --help.
- for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
- test -d "$ac_dir" || continue
- ac_builddir=.
-
-case "$ac_dir" in
-.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
-*)
- ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
- # A ".." for each directory in $ac_dir_suffix.
- ac_top_builddir_sub=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,/..,g;s,/,,'`
- case $ac_top_builddir_sub in
- "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
- *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
- esac ;;
-esac
-ac_abs_top_builddir=$ac_pwd
-ac_abs_builddir=$ac_pwd$ac_dir_suffix
-# for backward compatibility:
-ac_top_builddir=$ac_top_build_prefix
-
-case $srcdir in
- .) # We are building in place.
- ac_srcdir=.
- ac_top_srcdir=$ac_top_builddir_sub
- ac_abs_top_srcdir=$ac_pwd ;;
- [\\/]* | ?:[\\/]* ) # Absolute name.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir
- ac_abs_top_srcdir=$srcdir ;;
- *) # Relative name.
- ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_build_prefix$srcdir
- ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
-esac
-ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-
- cd "$ac_dir" || { ac_status=$?; continue; }
- # Check for guested configure.
- if test -f "$ac_srcdir/configure.gnu"; then
- echo &&
- $SHELL "$ac_srcdir/configure.gnu" --help=recursive
- elif test -f "$ac_srcdir/configure"; then
- echo &&
- $SHELL "$ac_srcdir/configure" --help=recursive
- else
- echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
- fi || ac_status=$?
- cd "$ac_pwd" || { ac_status=$?; break; }
- done
-fi
-
-test -n "$ac_init_help" && exit $ac_status
-if $ac_init_version; then
- cat <<\_ACEOF
-GNU autotoolset configure 0.11.5
-generated by GNU Autoconf 2.60
-
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
-2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
-This configure script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it.
-_ACEOF
- exit
-fi
-cat >config.log <<_ACEOF
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by GNU autotoolset $as_me 0.11.5, which was
-generated by GNU Autoconf 2.60. Invocation command line was
-
- $ $0 $@
-
-_ACEOF
-exec 5>>config.log
-{
-cat <<_ASUNAME
-## --------- ##
-## Platform. ##
-## --------- ##
-
-hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
-uname -m = `(uname -m) 2>/dev/null || echo unknown`
-uname -r = `(uname -r) 2>/dev/null || echo unknown`
-uname -s = `(uname -s) 2>/dev/null || echo unknown`
-uname -v = `(uname -v) 2>/dev/null || echo unknown`
-
-/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
-/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
-
-/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
-/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
-/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
-/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
-/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
-/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
-/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
-
-_ASUNAME
-
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- echo "PATH: $as_dir"
-done
-IFS=$as_save_IFS
-
-} >&5
-
-cat >&5 <<_ACEOF
-
-
-## ----------- ##
-## Core tests. ##
-## ----------- ##
-
-_ACEOF
-
-
-# Keep a trace of the command line.
-# Strip out --no-create and --no-recursion so they do not pile up.
-# Strip out --silent because we don't want to record it for future runs.
-# Also quote any args containing shell meta-characters.
-# Make two passes to allow for proper duplicate-argument suppression.
-ac_configure_args=
-ac_configure_args0=
-ac_configure_args1=
-ac_must_keep_next=false
-for ac_pass in 1 2
-do
- for ac_arg
- do
- case $ac_arg in
- -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil)
- continue ;;
- *\'*)
- ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- case $ac_pass in
- 1) ac_configure_args0="$ac_configure_args0 '$ac_arg'" ;;
- 2)
- ac_configure_args1="$ac_configure_args1 '$ac_arg'"
- if test $ac_must_keep_next = true; then
- ac_must_keep_next=false # Got value, back to normal.
- else
- case $ac_arg in
- *=* | --config-cache | -C | -disable-* | --disable-* \
- | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
- | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
- | -with-* | --with-* | -without-* | --without-* | --x)
- case "$ac_configure_args0 " in
- "$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
- esac
- ;;
- -* ) ac_must_keep_next=true ;;
- esac
- fi
- ac_configure_args="$ac_configure_args '$ac_arg'"
- ;;
- esac
- done
-done
-$as_unset ac_configure_args0 || test "${ac_configure_args0+set}" != set || { ac_configure_args0=; export ac_configure_args0; }
-$as_unset ac_configure_args1 || test "${ac_configure_args1+set}" != set || { ac_configure_args1=; export ac_configure_args1; }
-
-# When interrupted or exit'd, cleanup temporary files, and complete
-# config.log. We remove comments because anyway the quotes in there
-# would cause problems or look ugly.
-# WARNING: Use '\'' to represent an apostrophe within the trap.
-# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
-trap 'exit_status=$?
- # Save into config.log some information that might help in debugging.
- {
- echo
-
- cat <<\_ASBOX
-## ---------------- ##
-## Cache variables. ##
-## ---------------- ##
-_ASBOX
- echo
- # The following way of writing the cache mishandles newlines in values,
-(
- for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
- eval ac_val=\$$ac_var
- case $ac_val in #(
- *${as_nl}*)
- case $ac_var in #(
- *_cv_*) { echo "$as_me:$LINENO: WARNING: Cache variable $ac_var contains a newline." >&5
-echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;;
- esac
- case $ac_var in #(
- _ | IFS | as_nl) ;; #(
- *) $as_unset $ac_var ;;
- esac ;;
- esac
- done
- (set) 2>&1 |
- case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
- *${as_nl}ac_space=\ *)
- sed -n \
- "s/'\''/'\''\\\\'\'''\''/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
- ;; #(
- *)
- sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
- ;;
- esac |
- sort
-)
- echo
-
- cat <<\_ASBOX
-## ----------------- ##
-## Output variables. ##
-## ----------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_vars
- do
- eval ac_val=\$$ac_var
- case $ac_val in
- *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
- esac
- echo "$ac_var='\''$ac_val'\''"
- done | sort
- echo
-
- if test -n "$ac_subst_files"; then
- cat <<\_ASBOX
-## ------------------- ##
-## File substitutions. ##
-## ------------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_files
- do
- eval ac_val=\$$ac_var
- case $ac_val in
- *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
- esac
- echo "$ac_var='\''$ac_val'\''"
- done | sort
- echo
- fi
-
- if test -s confdefs.h; then
- cat <<\_ASBOX
-## ----------- ##
-## confdefs.h. ##
-## ----------- ##
-_ASBOX
- echo
- cat confdefs.h
- echo
- fi
- test "$ac_signal" != 0 &&
- echo "$as_me: caught signal $ac_signal"
- echo "$as_me: exit $exit_status"
- } >&5
- rm -f core *.core core.conftest.* &&
- rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
- exit $exit_status
-' 0
-for ac_signal in 1 2 13 15; do
- trap 'ac_signal='$ac_signal'; { (exit 1); exit 1; }' $ac_signal
-done
-ac_signal=0
-
-# confdefs.h avoids OS command line length limits that DEFS can exceed.
-rm -f -r conftest* confdefs.h
-
-# Predefined preprocessor variables.
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_NAME "$PACKAGE_NAME"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_VERSION "$PACKAGE_VERSION"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_STRING "$PACKAGE_STRING"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
-_ACEOF
-
-
-# Let the site file select an alternate cache file if it wants to.
-# Prefer explicitly selected file to automatically selected ones.
-if test -n "$CONFIG_SITE"; then
- set x "$CONFIG_SITE"
-elif test "x$prefix" != xNONE; then
- set x "$prefix/share/config.site" "$prefix/etc/config.site"
-else
- set x "$ac_default_prefix/share/config.site" \
- "$ac_default_prefix/etc/config.site"
-fi
-shift
-for ac_site_file
-do
- if test -r "$ac_site_file"; then
- { echo "$as_me:$LINENO: loading site script $ac_site_file" >&5
-echo "$as_me: loading site script $ac_site_file" >&6;}
- sed 's/^/| /' "$ac_site_file" >&5
- . "$ac_site_file"
- fi
-done
-
-if test -r "$cache_file"; then
- # Some versions of bash will fail to source /dev/null (special
- # files actually), so we avoid doing that.
- if test -f "$cache_file"; then
- { echo "$as_me:$LINENO: loading cache $cache_file" >&5
-echo "$as_me: loading cache $cache_file" >&6;}
- case $cache_file in
- [\\/]* | ?:[\\/]* ) . "$cache_file";;
- *) . "./$cache_file";;
- esac
- fi
-else
- { echo "$as_me:$LINENO: creating cache $cache_file" >&5
-echo "$as_me: creating cache $cache_file" >&6;}
- >$cache_file
-fi
-
-# Check that the precious variables saved in the cache have kept the same
-# value.
-ac_cache_corrupted=false
-for ac_var in $ac_precious_vars; do
- eval ac_old_set=\$ac_cv_env_${ac_var}_set
- eval ac_new_set=\$ac_env_${ac_var}_set
- eval ac_old_val=\$ac_cv_env_${ac_var}_value
- eval ac_new_val=\$ac_env_${ac_var}_value
- case $ac_old_set,$ac_new_set in
- set,)
- { echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
-echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,set)
- { echo "$as_me:$LINENO: error: \`$ac_var' was not set in the previous run" >&5
-echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,);;
- *)
- if test "x$ac_old_val" != "x$ac_new_val"; then
- { echo "$as_me:$LINENO: error: \`$ac_var' has changed since the previous run:" >&5
-echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
- { echo "$as_me:$LINENO: former value: $ac_old_val" >&5
-echo "$as_me: former value: $ac_old_val" >&2;}
- { echo "$as_me:$LINENO: current value: $ac_new_val" >&5
-echo "$as_me: current value: $ac_new_val" >&2;}
- ac_cache_corrupted=:
- fi;;
- esac
- # Pass precious variables to config.status.
- if test "$ac_new_set" = set; then
- case $ac_new_val in
- *\'*) ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
- *) ac_arg=$ac_var=$ac_new_val ;;
- esac
- case " $ac_configure_args " in
- *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
- *) ac_configure_args="$ac_configure_args '$ac_arg'" ;;
- esac
- fi
-done
-if $ac_cache_corrupted; then
- { echo "$as_me:$LINENO: error: changes in the environment can compromise the build" >&5
-echo "$as_me: error: changes in the environment can compromise the build" >&2;}
- { { echo "$as_me:$LINENO: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5
-echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;}
- { (exit 1); exit 1; }; }
-fi
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-
-
-am__api_version="1.9"
-ac_aux_dir=
-for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do
- if test -f "$ac_dir/install-sh"; then
- ac_aux_dir=$ac_dir
- ac_install_sh="$ac_aux_dir/install-sh -c"
- break
- elif test -f "$ac_dir/install.sh"; then
- ac_aux_dir=$ac_dir
- ac_install_sh="$ac_aux_dir/install.sh -c"
- break
- elif test -f "$ac_dir/shtool"; then
- ac_aux_dir=$ac_dir
- ac_install_sh="$ac_aux_dir/shtool install -c"
- break
- fi
-done
-if test -z "$ac_aux_dir"; then
- { { echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&5
-echo "$as_me: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&2;}
- { (exit 1); exit 1; }; }
-fi
-
-# These three variables are undocumented and unsupported,
-# and are intended to be withdrawn in a future Autoconf release.
-# They can cause serious problems if a builder's source tree is in a directory
-# whose full name contains unusual characters.
-ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
-ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
-ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
-
-
-# Find a good install program. We prefer a C program (faster),
-# so one script is as good as another. But avoid the broken or
-# incompatible versions:
-# SysV /etc/install, /usr/sbin/install
-# SunOS /usr/etc/install
-# IRIX /sbin/install
-# AIX /bin/install
-# AmigaOS /C/install, which installs bootblocks on floppy discs
-# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag
-# AFS /usr/afsws/bin/install, which mishandles nonexistent args
-# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
-# OS/2's system install, which has a completely different semantic
-# ./install, which can be erroneously created by make from ./install.sh.
-{ echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5
-echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6; }
-if test -z "$INSTALL"; then
-if test "${ac_cv_path_install+set}" = set; then
- echo $ECHO_N "(cached) $ECHO_C" >&6
-else
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- # Account for people who put trailing slashes in PATH elements.
-case $as_dir/ in
- ./ | .// | /cC/* | \
- /etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \
- ?:\\/os2\\/install\\/* | ?:\\/OS2\\/INSTALL\\/* | \
- /usr/ucb/* ) ;;
- *)
- # OSF1 and SCO ODT 3.0 have their own names for install.
- # Don't use installbsd from OSF since it installs stuff as root
- # by default.
- for ac_prog in ginstall scoinst install; do
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_prog$ac_exec_ext" && $as_executable_p "$as_dir/$ac_prog$ac_exec_ext"; }; then
- if test $ac_prog = install &&
- grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
- # AIX install. It has an incompatible calling convention.
- :
- elif test $ac_prog = install &&
- grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
- # program-specific install script used by HP pwplus--don't use.
- :
- else
- ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c"
- break 3
- fi
- fi
- done
- done
- ;;
-esac
-done
-IFS=$as_save_IFS
-
-
-fi
- if test "${ac_cv_path_install+set}" = set; then
- INSTALL=$ac_cv_path_install
- else
- # As a last resort, use the slow shell script. Don't cache a
- # value for INSTALL within a source directory, because that will
- # break other packages using the cache if that directory is
- # removed, or if the value is a relative name.
- INSTALL=$ac_install_sh
- fi
-fi
-{ echo "$as_me:$LINENO: result: $INSTALL" >&5
-echo "${ECHO_T}$INSTALL" >&6; }
-
-# Use test -z because SunOS4 sh mishandles braces in ${var-val}.
-# It thinks the first close brace ends the variable substitution.
-test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}'
-
-test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}'
-
-test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
-
-{ echo "$as_me:$LINENO: checking whether build environment is sane" >&5
-echo $ECHO_N "checking whether build environment is sane... $ECHO_C" >&6; }
-# Just in case
-sleep 1
-echo timestamp > conftest.file
-# Do `set' in a subshell so we don't clobber the current shell's
-# arguments. Must try -L first in case configure is actually a
-# symlink; some systems play weird games with the mod time of symlinks
-# (eg FreeBSD returns the mod time of the symlink's containing
-# directory).
-if (
- set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null`
- if test "$*" = "X"; then
- # -L didn't work.
- set X `ls -t $srcdir/configure conftest.file`
- fi
- rm -f conftest.file
- if test "$*" != "X $srcdir/configure conftest.file" \
- && test "$*" != "X conftest.file $srcdir/configure"; then
-
- # If neither matched, then we have a broken ls. This can happen
- # if, for instance, CONFIG_SHELL is bash and it inherits a
- # broken ls alias from the environment. This has actually
- # happened. Such a system could not be considered "sane".
- { { echo "$as_me:$LINENO: error: ls -t appears to fail. Make sure there is not a broken
-alias in your environment" >&5
-echo "$as_me: error: ls -t appears to fail. Make sure there is not a broken
-alias in your environment" >&2;}
- { (exit 1); exit 1; }; }
- fi
-
- test "$2" = conftest.file
- )
-then
- # Ok.
- :
-else
- { { echo "$as_me:$LINENO: error: newly created file is older than distributed files!
-Check your system clock" >&5
-echo "$as_me: error: newly created file is older than distributed files!
-Check your system clock" >&2;}
- { (exit 1); exit 1; }; }
-fi
-{ echo "$as_me:$LINENO: result: yes" >&5
-echo "${ECHO_T}yes" >&6; }
-test "$program_prefix" != NONE &&
- program_transform_name="s&^&$program_prefix&;$program_transform_name"
-# Use a double $ so make ignores it.
-test "$program_suffix" != NONE &&
- program_transform_name="s&\$&$program_suffix&;$program_transform_name"
-# Double any \ or $. echo might interpret backslashes.
-# By default was `s,x,x', remove it if useless.
-cat <<\_ACEOF >conftest.sed
-s/[\\$]/&&/g;s/;s,x,x,$//
-_ACEOF
-program_transform_name=`echo $program_transform_name | sed -f conftest.sed`
-rm -f conftest.sed
-
-# expand $ac_aux_dir to an absolute path
-am_aux_dir=`cd $ac_aux_dir && pwd`
-
-test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing"
-# Use eval to expand $SHELL
-if eval "$MISSING --run true"; then
- am_missing_run="$MISSING --run "
-else
- am_missing_run=
- { echo "$as_me:$LINENO: WARNING: \`missing' script is too old or missing" >&5
-echo "$as_me: WARNING: \`missing' script is too old or missing" >&2;}
-fi
-
-if mkdir -p --version . >/dev/null 2>&1 && test ! -d ./--version; then
- # We used to keeping the `.' as first argument, in order to
- # allow $(mkdir_p) to be used without argument. As in
- # $(mkdir_p) $(somedir)
- # where $(somedir) is conditionally defined. However this is wrong
- # for two reasons:
- # 1. if the package is installed by a user who cannot write `.'
- # make install will fail,
- # 2. the above comment should most certainly read
- # $(mkdir_p) $(DESTDIR)$(somedir)
- # so it does not work when $(somedir) is undefined and
- # $(DESTDIR) is not.
- # To support the latter case, we have to write
- # test -z "$(somedir)" || $(mkdir_p) $(DESTDIR)$(somedir),
- # so the `.' trick is pointless.
- mkdir_p='mkdir -p --'
-else
- # On NextStep and OpenStep, the `mkdir' command does not
- # recognize any option. It will interpret all options as
- # directories to create, and then abort because `.' already
- # exists.
- for d in ./-p ./--version;
- do
- test -d $d && rmdir $d
- done
- # $(mkinstalldirs) is defined by Automake if mkinstalldirs exists.
- if test -f "$ac_aux_dir/mkinstalldirs"; then
- mkdir_p='$(mkinstalldirs)'
- else
- mkdir_p='$(install_sh) -d'
- fi
-fi
-
-for ac_prog in gawk mawk nawk awk
-do
- # Extract the first word of "$ac_prog", so it can be a program name with args.
-set dummy $ac_prog; ac_word=$2
-{ echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; }
-if test "${ac_cv_prog_AWK+set}" = set; then
- echo $ECHO_N "(cached) $ECHO_C" >&6
-else
- if test -n "$AWK"; then
- ac_cv_prog_AWK="$AWK" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; }; then
- ac_cv_prog_AWK="$ac_prog"
- echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
-done
-IFS=$as_save_IFS
-
-fi
-fi
-AWK=$ac_cv_prog_AWK
-if test -n "$AWK"; then
- { echo "$as_me:$LINENO: result: $AWK" >&5
-echo "${ECHO_T}$AWK" >&6; }
-else
- { echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6; }
-fi
-
-
- test -n "$AWK" && break
-done
-
-{ echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5
-echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6; }
-set x ${MAKE-make}; ac_make=`echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'`
-if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then
- echo $ECHO_N "(cached) $ECHO_C" >&6
-else
- cat >conftest.make <<\_ACEOF
-SHELL = /bin/sh
-all:
- @echo '@@@%%%=$(MAKE)=@@@%%%'
-_ACEOF
-# GNU make sometimes prints "make[1]: Entering...", which would confuse us.
-case `${MAKE-make} -f conftest.make 2>/dev/null` in
- *@@@%%%=?*=@@@%%%*)
- eval ac_cv_prog_make_${ac_make}_set=yes;;
- *)
- eval ac_cv_prog_make_${ac_make}_set=no;;
-esac
-rm -f conftest.make
-fi
-if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
- { echo "$as_me:$LINENO: result: yes" >&5
-echo "${ECHO_T}yes" >&6; }
- S...
[truncated message content] |
|
From: <mro...@us...> - 2007-05-14 01:06:07
|
Revision: 38
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=38&view=rev
Author: mroberto
Date: 2007-05-13 18:06:09 -0700 (Sun, 13 May 2007)
Log Message:
-----------
configure.ac: No longer use AC_CONFIG_AUX_DIR, now use
AC_CONFIG_SRCDIR.
Modified Paths:
--------------
trunk/ChangeLog
trunk/configure
trunk/configure.ac
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2007-05-14 00:53:59 UTC (rev 37)
+++ trunk/ChangeLog 2007-05-14 01:06:09 UTC (rev 38)
@@ -1,5 +1,10 @@
2007-05-13 Marcelo Roberto Jimenez <mro...@ce...>
+ * configure.ac: No longer use AC_CONFIG_AUX_DIR, now use
+ AC_CONFIG_SRCDIR.
+
+2007-05-13 Marcelo Roberto Jimenez <mro...@ce...>
+
* using_automake_autoconf.texi, fortran.texi, gnu_build_system.texi,
good_code.texi, legal.texi, installing_gnu_software.texi,
philosophy.texi, using_autotools.texi, makefiles.texi, gnu_emacs.texi,
Modified: trunk/configure
===================================================================
--- trunk/configure 2007-05-14 00:53:59 UTC (rev 37)
+++ trunk/configure 2007-05-14 01:06:09 UTC (rev 38)
@@ -1,10 +1,11 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.59 for GNU autotoolset 0.11.5.
+# Generated by GNU Autoconf 2.60 for GNU autotoolset 0.11.5.
#
# Report bugs to <Marcelo Roberto Jimenez <mro...@ce...>>.
#
-# Copyright (C) 2003 Free Software Foundation, Inc.
+# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
+# 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.
## --------------------- ##
@@ -18,11 +19,35 @@
# Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
-elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
- set -o posix
+ setopt NO_GLOB_SUBST
+else
+ case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
fi
+BIN_SH=xpg4; export BIN_SH # for Tru64
DUALCASE=1; export DUALCASE # for MKS sh
+
+# PATH needs CR
+# Avoid depending upon Character Ranges.
+as_cr_letters='abcdefghijklmnopqrstuvwxyz'
+as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
+as_cr_Letters=$as_cr_letters$as_cr_LETTERS
+as_cr_digits='0123456789'
+as_cr_alnum=$as_cr_Letters$as_cr_digits
+
+# The user is always right.
+if test "${PATH_SEPARATOR+set}" != set; then
+ echo "#! /bin/sh" >conf$$.sh
+ echo "exit 0" >>conf$$.sh
+ chmod +x conf$$.sh
+ if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
+ PATH_SEPARATOR=';'
+ else
+ PATH_SEPARATOR=:
+ fi
+ rm -f conf$$.sh
+fi
+
# Support unset when possible.
if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
as_unset=unset
@@ -31,8 +56,43 @@
fi
+# IFS
+# We need space, tab and new line, in precisely that order. Quoting is
+# there to prevent editors from complaining about space-tab.
+# (If _AS_PATH_WALK were called with IFS unset, it would disable word
+# splitting by setting IFS to empty value.)
+as_nl='
+'
+IFS=" "" $as_nl"
+
+# Find who we are. Look in the path if we contain no directory separator.
+case $0 in
+ *[\\/]* ) as_myself=$0 ;;
+ *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
+done
+IFS=$as_save_IFS
+
+ ;;
+esac
+# We did not find ourselves, most probably we were run as `sh COMMAND'
+# in which case we are not to be found in the path.
+if test "x$as_myself" = x; then
+ as_myself=$0
+fi
+if test ! -f "$as_myself"; then
+ echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
+ { (exit 1); exit 1; }
+fi
+
# Work around bugs in pre-3.0 UWIN ksh.
-$as_unset ENV MAIL MAILPATH
+for as_var in ENV MAIL MAILPATH
+do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
+done
PS1='$ '
PS2='> '
PS4='+ '
@@ -46,18 +106,19 @@
if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then
eval $as_var=C; export $as_var
else
- $as_unset $as_var
+ ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
fi
done
# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1; then
+if expr a : '\(a\)' >/dev/null 2>&1 &&
+ test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
-if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then
+if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
as_basename=basename
else
as_basename=false
@@ -65,157 +126,386 @@
# Name of the executable.
-as_me=`$as_basename "$0" ||
+as_me=`$as_basename -- "$0" ||
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)$' \| \
- . : '\(.\)' 2>/dev/null ||
+ X"$0" : 'X\(/\)' \| . 2>/dev/null ||
echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }
- /^X\/\(\/\/\)$/{ s//\1/; q; }
- /^X\/\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
+ sed '/^.*\/\([^/][^/]*\)\/*$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+# CDPATH.
+$as_unset CDPATH
-# PATH needs CR, and LINENO needs CR and PATH.
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- echo "#! /bin/sh" >conf$$.sh
- echo "exit 0" >>conf$$.sh
- chmod +x conf$$.sh
- if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
- PATH_SEPARATOR=';'
- else
- PATH_SEPARATOR=:
- fi
- rm -f conf$$.sh
+if test "x$CONFIG_SHELL" = x; then
+ if (eval ":") 2>/dev/null; then
+ as_have_required=yes
+else
+ as_have_required=no
fi
+ if test $as_have_required = yes && (eval ":
+(as_func_return () {
+ (exit \$1)
+}
+as_func_success () {
+ as_func_return 0
+}
+as_func_failure () {
+ as_func_return 1
+}
+as_func_ret_success () {
+ return 0
+}
+as_func_ret_failure () {
+ return 1
+}
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" || {
- # Find who we are. Look in the path if we contain no path at all
- # relative or not.
- case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
+exitcode=0
+if as_func_success; then
+ :
+else
+ exitcode=1
+ echo as_func_success failed.
+fi
- ;;
- esac
- # We did not find ourselves, most probably we were run as `sh COMMAND'
- # in which case we are not to be found in the path.
- if test "x$as_myself" = x; then
- as_myself=$0
- fi
- if test ! -f "$as_myself"; then
- { echo "$as_me: error: cannot find myself; rerun with an absolute path" >&2
- { (exit 1); exit 1; }; }
- fi
- case $CONFIG_SHELL in
- '')
+if as_func_failure; then
+ exitcode=1
+ echo as_func_failure succeeded.
+fi
+
+if as_func_ret_success; then
+ :
+else
+ exitcode=1
+ echo as_func_ret_success failed.
+fi
+
+if as_func_ret_failure; then
+ exitcode=1
+ echo as_func_ret_failure succeeded.
+fi
+
+if ( set x; as_func_ret_success y && test x = \"\$1\" ); then
+ :
+else
+ exitcode=1
+ echo positional parameters were not saved.
+fi
+
+test \$exitcode = 0) || { (exit 1); exit 1; }
+
+(
+ as_lineno_1=\$LINENO
+ as_lineno_2=\$LINENO
+ test \"x\$as_lineno_1\" != \"x\$as_lineno_2\" &&
+ test \"x\`expr \$as_lineno_1 + 1\`\" = \"x\$as_lineno_2\") || { (exit 1); exit 1; }
+") 2> /dev/null; then
+ :
+else
+ as_candidate_shells=
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
+for as_dir in /usr/bin/posix$PATH_SEPARATOR/bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
- for as_base in sh bash ksh sh5; do
- case $as_dir in
+ case $as_dir in
/*)
- if ("$as_dir/$as_base" -c '
+ for as_base in sh bash ksh sh5; do
+ as_candidate_shells="$as_candidate_shells $as_dir/$as_base"
+ done;;
+ esac
+done
+IFS=$as_save_IFS
+
+
+ for as_shell in $as_candidate_shells $SHELL; do
+ # Try only shells that exist, to save several forks.
+ if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
+ { ("$as_shell") 2> /dev/null <<\_ASEOF
+# Be Bourne compatible
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
+ emulate sh
+ NULLCMD=:
+ # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+ setopt NO_GLOB_SUBST
+else
+ case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
+fi
+BIN_SH=xpg4; export BIN_SH # for Tru64
+DUALCASE=1; export DUALCASE # for MKS sh
+
+:
+_ASEOF
+}; then
+ CONFIG_SHELL=$as_shell
+ as_have_required=yes
+ if { "$as_shell" 2> /dev/null <<\_ASEOF
+# Be Bourne compatible
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
+ emulate sh
+ NULLCMD=:
+ # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+ setopt NO_GLOB_SUBST
+else
+ case `(set -o) 2>/dev/null` in *posix*) set -o posix;; esac
+fi
+BIN_SH=xpg4; export BIN_SH # for Tru64
+DUALCASE=1; export DUALCASE # for MKS sh
+
+:
+(as_func_return () {
+ (exit $1)
+}
+as_func_success () {
+ as_func_return 0
+}
+as_func_failure () {
+ as_func_return 1
+}
+as_func_ret_success () {
+ return 0
+}
+as_func_ret_failure () {
+ return 1
+}
+
+exitcode=0
+if as_func_success; then
+ :
+else
+ exitcode=1
+ echo as_func_success failed.
+fi
+
+if as_func_failure; then
+ exitcode=1
+ echo as_func_failure succeeded.
+fi
+
+if as_func_ret_success; then
+ :
+else
+ exitcode=1
+ echo as_func_ret_success failed.
+fi
+
+if as_func_ret_failure; then
+ exitcode=1
+ echo as_func_ret_failure succeeded.
+fi
+
+if ( set x; as_func_ret_success y && test x = "$1" ); then
+ :
+else
+ exitcode=1
+ echo positional parameters were not saved.
+fi
+
+test $exitcode = 0) || { (exit 1); exit 1; }
+
+(
as_lineno_1=$LINENO
as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" ') 2>/dev/null; then
- $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
- $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
- CONFIG_SHELL=$as_dir/$as_base
- export CONFIG_SHELL
- exec "$CONFIG_SHELL" "$0" ${1+"$@"}
- fi;;
- esac
- done
-done
-;;
- esac
+ test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2") || { (exit 1); exit 1; }
+_ASEOF
+}; then
+ break
+fi
+
+fi
+
+ done
+
+ if test "x$CONFIG_SHELL" != x; then
+ for as_var in BASH_ENV ENV
+ do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
+ done
+ export CONFIG_SHELL
+ exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"}
+fi
+
+
+ if test $as_have_required = no; then
+ echo This script requires a shell more modern than all the
+ echo shells that I found on your system. Please install a
+ echo modern shell, or manually run the script under such a
+ echo shell if you do have one.
+ { (exit 1); exit 1; }
+fi
+
+
+fi
+
+fi
+
+
+
+(eval "as_func_return () {
+ (exit \$1)
+}
+as_func_success () {
+ as_func_return 0
+}
+as_func_failure () {
+ as_func_return 1
+}
+as_func_ret_success () {
+ return 0
+}
+as_func_ret_failure () {
+ return 1
+}
+
+exitcode=0
+if as_func_success; then
+ :
+else
+ exitcode=1
+ echo as_func_success failed.
+fi
+
+if as_func_failure; then
+ exitcode=1
+ echo as_func_failure succeeded.
+fi
+
+if as_func_ret_success; then
+ :
+else
+ exitcode=1
+ echo as_func_ret_success failed.
+fi
+
+if as_func_ret_failure; then
+ exitcode=1
+ echo as_func_ret_failure succeeded.
+fi
+
+if ( set x; as_func_ret_success y && test x = \"\$1\" ); then
+ :
+else
+ exitcode=1
+ echo positional parameters were not saved.
+fi
+
+test \$exitcode = 0") || {
+ echo No shell found that supports shell functions.
+ echo Please tell aut...@gn... about your system,
+ echo including any error possibly output before this
+ echo message
+}
+
+
+
+ as_lineno_1=$LINENO
+ as_lineno_2=$LINENO
+ test "x$as_lineno_1" != "x$as_lineno_2" &&
+ test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2" || {
+
# Create $as_me.lineno as a copy of $as_myself, but with $LINENO
# uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line before each line; the second 'sed' does the real
- # work. The second script uses 'N' to pair each line-number line
- # with the numbered line, and appends trailing '-' during
- # substitution so that $LINENO is not a special case at line end.
+ # line-number line after each line using $LINENO; the second 'sed'
+ # does the real work. The second script uses 'N' to pair each
+ # line-number line with the line containing $LINENO, and appends
+ # trailing '-' during substitution so that $LINENO is not a special
+ # case at line end.
# (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # second 'sed' script. Blame Lee E. McMahon for sed's syntax. :-)
- sed '=' <$as_myself |
+ # scripts with optimization help from Paolo Bonzini. Blame Lee
+ # E. McMahon (1931-1989) for sed's syntax. :-)
+ sed -n '
+ p
+ /[$]LINENO/=
+ ' <$as_myself |
sed '
+ s/[$]LINENO.*/&-/
+ t lineno
+ b
+ :lineno
N
- s,$,-,
- : loop
- s,^\(['$as_cr_digits']*\)\(.*\)[$]LINENO\([^'$as_cr_alnum'_]\),\1\2\1\3,
+ :loop
+ s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
t loop
- s,-$,,
- s,^['$as_cr_digits']*\n,,
+ s/-\n.*//
' >$as_me.lineno &&
- chmod +x $as_me.lineno ||
+ chmod +x "$as_me.lineno" ||
{ echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
{ (exit 1); exit 1; }; }
# Don't try to exec as it changes $[0], causing all sort of problems
# (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensible to this).
- . ./$as_me.lineno
+ # original and so on. Autoconf is especially sensitive to this).
+ . "./$as_me.lineno"
# Exit status is that of the last command.
exit
}
-case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
- *c*,-n*) ECHO_N= ECHO_C='
-' ECHO_T=' ' ;;
- *c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
- *) ECHO_N= ECHO_C='\c' ECHO_T= ;;
+if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
+ as_dirname=dirname
+else
+ as_dirname=false
+fi
+
+ECHO_C= ECHO_N= ECHO_T=
+case `echo -n x` in
+-n*)
+ case `echo 'x\c'` in
+ *c*) ECHO_T=' ';; # ECHO_T is single tab character.
+ *) ECHO_C='\c';;
+ esac;;
+*)
+ ECHO_N='-n';;
esac
-if expr a : '\(a\)' >/dev/null 2>&1; then
+if expr a : '\(a\)' >/dev/null 2>&1 &&
+ test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
rm -f conf$$ conf$$.exe conf$$.file
+if test -d conf$$.dir; then
+ rm -f conf$$.dir/conf$$.file
+else
+ rm -f conf$$.dir
+ mkdir conf$$.dir
+fi
echo >conf$$.file
if ln -s conf$$.file conf$$ 2>/dev/null; then
- # We could just check for DJGPP; but this test a) works b) is more generic
- # and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
- if test -f conf$$.exe; then
- # Don't use ln at all; we don't have any links
+ as_ln_s='ln -s'
+ # ... but there are two gotchas:
+ # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
+ # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
+ # In both cases, we have to default to `cp -p'.
+ ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -p'
- else
- as_ln_s='ln -s'
- fi
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -p'
fi
-rm -f conf$$ conf$$.exe conf$$.file
+rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
+rmdir conf$$.dir 2>/dev/null
if mkdir -p . 2>/dev/null; then
as_mkdir_p=:
@@ -224,7 +514,19 @@
as_mkdir_p=false
fi
-as_executable_p="test -f"
+# Find out whether ``test -x'' works. Don't use a zero-byte file, as
+# systems may use methods other than mode bits to determine executability.
+cat >conf$$.file <<_ASEOF
+#! /bin/sh
+exit 0
+_ASEOF
+chmod +x conf$$.file
+if test -x conf$$.file >/dev/null 2>&1; then
+ as_executable_p="test -x"
+else
+ as_executable_p=:
+fi
+rm -f conf$$.file
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
@@ -233,39 +535,27 @@
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-# IFS
-# We need space, tab and new line, in precisely that order.
-as_nl='
-'
-IFS=" $as_nl"
-# CDPATH.
-$as_unset CDPATH
+exec 7<&0 </dev/null 6>&1
-
# Name of the host.
# hostname on some systems (SVR3.2, Linux) returns a bogus exit status,
# so uname gets run too.
ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
-exec 6>&1
-
#
# Initializations.
#
ac_default_prefix=/usr/local
+ac_clean_files=
ac_config_libobj_dir=.
+LIBOBJS=
cross_compiling=no
subdirs=
MFLAGS=
MAKEFLAGS=
SHELL=${CONFIG_SHELL-/bin/sh}
-# Maximum number of lines to put in a shell here document.
-# This variable seems obsolete. It should probably be removed, and
-# only ac_max_sed_lines should be used.
-: ${ac_max_here_lines=38}
-
# Identity of this package.
PACKAGE_NAME='GNU autotoolset'
PACKAGE_TARNAME='autotoolset'
@@ -273,6 +563,7 @@
PACKAGE_STRING='GNU autotoolset 0.11.5'
PACKAGE_BUGREPORT='Marcelo Roberto Jimenez <mro...@ce...>'
+ac_unique_file="src/Makefile.am"
# Factoring default headers for most tests.
ac_includes_default="\
#include <stdio.h>
@@ -301,18 +592,117 @@
#endif
#if HAVE_INTTYPES_H
# include <inttypes.h>
-#else
-# if HAVE_STDINT_H
-# include <stdint.h>
-# endif
#endif
+#if HAVE_STDINT_H
+# include <stdint.h>
+#endif
#if HAVE_UNISTD_H
# include <unistd.h>
#endif"
-ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS INSTALL_PROGRAM INSTALL_SCRIPT INSTALL_DATA CYGPATH_W PACKAGE VERSION ACLOCAL AUTOCONF AUTOMAKE AUTOHEADER MAKEINFO install_sh STRIP ac_ct_STRIP INSTALL_STRIP_PROGRAM mkdir_p AWK SET_MAKE am__leading_dot AMTAR am__tar am__untar CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT DEPDIR am__include am__quote AMDEP_TRUE AMDEP_FALSE AMDEPBACKSLASH CCDEPMODE am__fastdepCC_TRUE am__fastdepCC_FALSE LN_S RANLIB ac_ct_RANLIB BASH TXTC PERL SHAR ZCAT EMACS EMACSLOADPATH lispdir ALLOCA CPP EGREP LIBOBJS LTLIBOBJS'
+ac_subst_vars='SHELL
+PATH_SEPARATOR
+PACKAGE_NAME
+PACKAGE_TARNAME
+PACKAGE_VERSION
+PACKAGE_STRING
+PACKAGE_BUGREPORT
+exec_prefix
+prefix
+program_transform_name
+bindir
+sbindir
+libexecdir
+datarootdir
+datadir
+sysconfdir
+sharedstatedir
+localstatedir
+includedir
+oldincludedir
+docdir
+infodir
+htmldir
+dvidir
+pdfdir
+psdir
+libdir
+localedir
+mandir
+DEFS
+ECHO_C
+ECHO_N
+ECHO_T
+LIBS
+build_alias
+host_alias
+target_alias
+INSTALL_PROGRAM
+INSTALL_SCRIPT
+INSTALL_DATA
+CYGPATH_W
+PACKAGE
+VERSION
+ACLOCAL
+AUTOCONF
+AUTOMAKE
+AUTOHEADER
+MAKEINFO
+install_sh
+STRIP
+INSTALL_STRIP_PROGRAM
+mkdir_p
+AWK
+SET_MAKE
+am__leading_dot
+AMTAR
+am__tar
+am__untar
+CC
+CFLAGS
+LDFLAGS
+CPPFLAGS
+ac_ct_CC
+EXEEXT
+OBJEXT
+DEPDIR
+am__include
+am__quote
+AMDEP_TRUE
+AMDEP_FALSE
+AMDEPBACKSLASH
+CCDEPMODE
+am__fastdepCC_TRUE
+am__fastdepCC_FALSE
+LN_S
+RANLIB
+BASH
+TXTC
+PERL
+SHAR
+ZCAT
+EMACS
+EMACSLOADPATH
+lispdir
+ALLOCA
+CPP
+GREP
+EGREP
+LIBOBJS
+LTLIBOBJS'
ac_subst_files=''
+ ac_precious_vars='build_alias
+host_alias
+target_alias
+CC
+CFLAGS
+LDFLAGS
+CPPFLAGS
+EMACS
+EMACSLOADPATH
+CPP'
+
# Initialize some variables set by options.
ac_init_help=
ac_init_version=false
@@ -338,34 +728,48 @@
# and all the variables that are supposed to be based on exec_prefix
# by default will actually change.
# Use braces instead of parens because sh, perl, etc. also accept them.
+# (The list follows the same order as the GNU Coding Standards.)
bindir='${exec_prefix}/bin'
sbindir='${exec_prefix}/sbin'
libexecdir='${exec_prefix}/libexec'
-datadir='${prefix}/share'
+datarootdir='${prefix}/share'
+datadir='${datarootdir}'
sysconfdir='${prefix}/etc'
sharedstatedir='${prefix}/com'
localstatedir='${prefix}/var'
-libdir='${exec_prefix}/lib'
includedir='${prefix}/include'
oldincludedir='/usr/include'
-infodir='${prefix}/info'
-mandir='${prefix}/man'
+docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
+infodir='${datarootdir}/info'
+htmldir='${docdir}'
+dvidir='${docdir}'
+pdfdir='${docdir}'
+psdir='${docdir}'
+libdir='${exec_prefix}/lib'
+localedir='${datarootdir}/locale'
+mandir='${datarootdir}/man'
ac_prev=
+ac_dashdash=
for ac_option
do
# If the previous option needs an argument, assign it.
if test -n "$ac_prev"; then
- eval "$ac_prev=\$ac_option"
+ eval $ac_prev=\$ac_option
ac_prev=
continue
fi
- ac_optarg=`expr "x$ac_option" : 'x[^=]*=\(.*\)'`
+ case $ac_option in
+ *=*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
+ *) ac_optarg=yes ;;
+ esac
# Accept the important Cygnus configure options, so we can diagnose typos.
- case $ac_option in
+ case $ac_dashdash$ac_option in
+ --)
+ ac_dashdash=yes ;;
-bindir | --bindir | --bindi | --bind | --bin | --bi)
ac_prev=bindir ;;
@@ -387,12 +791,18 @@
--config-cache | -C)
cache_file=config.cache ;;
- -datadir | --datadir | --datadi | --datad | --data | --dat | --da)
+ -datadir | --datadir | --datadi | --datad)
ac_prev=datadir ;;
- -datadir=* | --datadir=* | --datadi=* | --datad=* | --data=* | --dat=* \
- | --da=*)
+ -datadir=* | --datadir=* | --datadi=* | --datad=*)
datadir=$ac_optarg ;;
+ -datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
+ | --dataroo | --dataro | --datar)
+ ac_prev=datarootdir ;;
+ -datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
+ | --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
+ datarootdir=$ac_optarg ;;
+
-disable-* | --disable-*)
ac_feature=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
# Reject names that are not valid shell variable names.
@@ -400,8 +810,18 @@
{ echo "$as_me: error: invalid feature name: $ac_feature" >&2
{ (exit 1); exit 1; }; }
ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- eval "enable_$ac_feature=no" ;;
+ eval enable_$ac_feature=no ;;
+ -docdir | --docdir | --docdi | --doc | --do)
+ ac_prev=docdir ;;
+ -docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
+ docdir=$ac_optarg ;;
+
+ -dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
+ ac_prev=dvidir ;;
+ -dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
+ dvidir=$ac_optarg ;;
+
-enable-* | --enable-*)
ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
# Reject names that are not valid shell variable names.
@@ -409,11 +829,7 @@
{ echo "$as_me: error: invalid feature name: $ac_feature" >&2
{ (exit 1); exit 1; }; }
ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- case $ac_option in
- *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
- *) ac_optarg=yes ;;
- esac
- eval "enable_$ac_feature='$ac_optarg'" ;;
+ eval enable_$ac_feature=\$ac_optarg ;;
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
| --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
@@ -440,6 +856,12 @@
-host=* | --host=* | --hos=* | --ho=*)
host_alias=$ac_optarg ;;
+ -htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
+ ac_prev=htmldir ;;
+ -htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
+ | --ht=*)
+ htmldir=$ac_optarg ;;
+
-includedir | --includedir | --includedi | --included | --include \
| --includ | --inclu | --incl | --inc)
ac_prev=includedir ;;
@@ -464,13 +886,16 @@
| --libexe=* | --libex=* | --libe=*)
libexecdir=$ac_optarg ;;
+ -localedir | --localedir | --localedi | --localed | --locale)
+ ac_prev=localedir ;;
+ -localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
+ localedir=$ac_optarg ;;
+
-localstatedir | --localstatedir | --localstatedi | --localstated \
- | --localstate | --localstat | --localsta | --localst \
- | --locals | --local | --loca | --loc | --lo)
+ | --localstate | --localstat | --localsta | --localst | --locals)
ac_prev=localstatedir ;;
-localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
- | --localstate=* | --localstat=* | --localsta=* | --localst=* \
- | --locals=* | --local=* | --loca=* | --loc=* | --lo=*)
+ | --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
localstatedir=$ac_optarg ;;
-mandir | --mandir | --mandi | --mand | --man | --ma | --m)
@@ -535,6 +960,16 @@
| --progr-tra=* | --program-tr=* | --program-t=*)
program_transform_name=$ac_optarg ;;
+ -pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
+ ac_prev=pdfdir ;;
+ -pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
+ pdfdir=$ac_optarg ;;
+
+ -psdir | --psdir | --psdi | --psd | --ps)
+ ac_prev=psdir ;;
+ -psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
+ psdir=$ac_optarg ;;
+
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
silent=yes ;;
@@ -591,11 +1026,7 @@
{ echo "$as_me: error: invalid package name: $ac_package" >&2
{ (exit 1); exit 1; }; }
ac_package=`echo $ac_package| sed 's/-/_/g'`
- case $ac_option in
- *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
- *) ac_optarg=yes ;;
- esac
- eval "with_$ac_package='$ac_optarg'" ;;
+ eval with_$ac_package=\$ac_optarg ;;
-without-* | --without-*)
ac_package=`expr "x$ac_option" : 'x-*without-\(.*\)'`
@@ -604,7 +1035,7 @@
{ echo "$as_me: error: invalid package name: $ac_package" >&2
{ (exit 1); exit 1; }; }
ac_package=`echo $ac_package | sed 's/-/_/g'`
- eval "with_$ac_package=no" ;;
+ eval with_$ac_package=no ;;
--x)
# Obsolete; use --with-x.
@@ -635,8 +1066,7 @@
expr "x$ac_envvar" : ".*[^_$as_cr_alnum]" >/dev/null &&
{ echo "$as_me: error: invalid variable name: $ac_envvar" >&2
{ (exit 1); exit 1; }; }
- ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`
- eval "$ac_envvar='$ac_optarg'"
+ eval $ac_envvar=\$ac_optarg
export $ac_envvar ;;
*)
@@ -656,29 +1086,21 @@
{ (exit 1); exit 1; }; }
fi
-# Be sure to have absolute paths.
-for ac_var in exec_prefix prefix
+# Be sure to have absolute directory names.
+for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
+ datadir sysconfdir sharedstatedir localstatedir includedir \
+ oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
+ libdir localedir mandir
do
- eval ac_val=$`echo $ac_var`
+ eval ac_val=\$$ac_var
case $ac_val in
- [\\/$]* | ?:[\\/]* | NONE | '' ) ;;
- *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
- { (exit 1); exit 1; }; };;
+ [\\/$]* | ?:[\\/]* ) continue;;
+ NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
esac
+ { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
+ { (exit 1); exit 1; }; }
done
-# Be sure to have absolute paths.
-for ac_var in bindir sbindir libexecdir datadir sysconfdir sharedstatedir \
- localstatedir libdir includedir oldincludedir infodir mandir
-do
- eval ac_val=$`echo $ac_var`
- case $ac_val in
- [\\/$]* | ?:[\\/]* ) ;;
- *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
- { (exit 1); exit 1; }; };;
- esac
-done
-
# There might be people who depend on the old broken behavior: `$host'
# used to hold the argument of --host etc.
# FIXME: To remove some day.
@@ -703,82 +1125,76 @@
test "$silent" = yes && exec 6>/dev/null
+ac_pwd=`pwd` && test -n "$ac_pwd" &&
+ac_ls_di=`ls -di .` &&
+ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
+ { echo "$as_me: error: Working directory cannot be determined" >&2
+ { (exit 1); exit 1; }; }
+test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
+ { echo "$as_me: error: pwd does not report name of working directory" >&2
+ { (exit 1); exit 1; }; }
+
+
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
ac_srcdir_defaulted=yes
- # Try the directory containing this script, then its parent.
- ac_confdir=`(dirname "$0") 2>/dev/null ||
+ # Try the directory containing this script, then the parent directory.
+ ac_confdir=`$as_dirname -- "$0" ||
$as_expr X"$0" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$0" : 'X\(//\)[^/]' \| \
X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| \
- . : '\(.\)' 2>/dev/null ||
+ X"$0" : 'X\(/\)' \| . 2>/dev/null ||
echo X"$0" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
- /^X\(\/\/\)[^/].*/{ s//\1/; q; }
- /^X\(\/\/\)$/{ s//\1/; q; }
- /^X\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)[^/].*/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
srcdir=$ac_confdir
- if test ! -r $srcdir/$ac_unique_file; then
+ if test ! -r "$srcdir/$ac_unique_file"; then
srcdir=..
fi
else
ac_srcdir_defaulted=no
fi
-if test ! -r $srcdir/$ac_unique_file; then
- if test "$ac_srcdir_defaulted" = yes; then
- { echo "$as_me: error: cannot find sources ($ac_unique_file) in $ac_confdir or .." >&2
+if test ! -r "$srcdir/$ac_unique_file"; then
+ test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
+ { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2
{ (exit 1); exit 1; }; }
- else
- { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2
+fi
+ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
+ac_abs_confdir=`(
+ cd "$srcdir" && test -r "./$ac_unique_file" || { echo "$as_me: error: $ac_msg" >&2
{ (exit 1); exit 1; }; }
- fi
+ pwd)`
+# When building in place, set srcdir=.
+if test "$ac_abs_confdir" = "$ac_pwd"; then
+ srcdir=.
fi
-(cd $srcdir && test -r ./$ac_unique_file) 2>/dev/null ||
- { echo "$as_me: error: sources are in $srcdir, but \`cd $srcdir' does not work" >&2
- { (exit 1); exit 1; }; }
-srcdir=`echo "$srcdir" | sed 's%\([^\\/]\)[\\/]*$%\1%'`
-ac_env_build_alias_set=${build_alias+set}
-ac_env_build_alias_value=$build_alias
-ac_cv_env_build_alias_set=${build_alias+set}
-ac_cv_env_build_alias_value=$build_alias
-ac_env_host_alias_set=${host_alias+set}
-ac_env_host_alias_value=$host_alias
-ac_cv_env_host_alias_set=${host_alias+set}
-ac_cv_env_host_alias_value=$host_alias
-ac_env_target_alias_set=${target_alias+set}
-ac_env_target_alias_value=$target_alias
-ac_cv_env_target_alias_set=${target_alias+set}
-ac_cv_env_target_alias_value=$target_alias
-ac_env_CC_set=${CC+set}
-ac_env_CC_value=$CC
-ac_cv_env_CC_set=${CC+set}
-ac_cv_env_CC_value=$CC
-ac_env_CFLAGS_set=${CFLAGS+set}
-ac_env_CFLAGS_value=$CFLAGS
-ac_cv_env_CFLAGS_set=${CFLAGS+set}
-ac_cv_env_CFLAGS_value=$CFLAGS
-ac_env_LDFLAGS_set=${LDFLAGS+set}
-ac_env_LDFLAGS_value=$LDFLAGS
-ac_cv_env_LDFLAGS_set=${LDFLAGS+set}
-ac_cv_env_LDFLAGS_value=$LDFLAGS
-ac_env_CPPFLAGS_set=${CPPFLAGS+set}
-ac_env_CPPFLAGS_value=$CPPFLAGS
-ac_cv_env_CPPFLAGS_set=${CPPFLAGS+set}
-ac_cv_env_CPPFLAGS_value=$CPPFLAGS
-ac_env_EMACS_set=${EMACS+set}
-ac_env_EMACS_value=$EMACS
-ac_cv_env_EMACS_set=${EMACS+set}
-ac_cv_env_EMACS_value=$EMACS
-ac_env_EMACSLOADPATH_set=${EMACSLOADPATH+set}
-ac_env_EMACSLOADPATH_value=$EMACSLOADPATH
-ac_cv_env_EMACSLOADPATH_set=${EMACSLOADPATH+set}
-ac_cv_env_EMACSLOADPATH_value=$EMACSLOADPATH
-ac_env_CPP_set=${CPP+set}
-ac_env_CPP_value=$CPP
-ac_cv_env_CPP_set=${CPP+set}
-ac_cv_env_CPP_value=$CPP
+# Remove unnecessary trailing slashes from srcdir.
+# Double slashes in file names in object file debugging info
+# mess up M-x gdb in Emacs.
+case $srcdir in
+*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
+esac
+for ac_var in $ac_precious_vars; do
+ eval ac_env_${ac_var}_set=\${${ac_var}+set}
+ eval ac_env_${ac_var}_value=\$${ac_var}
+ eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
+ eval ac_cv_env_${ac_var}_value=\$${ac_var}
+done
#
# Report the --help message.
@@ -807,9 +1223,6 @@
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or \`..']
-_ACEOF
-
- cat <<_ACEOF
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[$ac_default_prefix]
@@ -827,15 +1240,22 @@
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
- --datadir=DIR read-only architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
- --infodir=DIR info documentation [PREFIX/info]
- --mandir=DIR man documentation [PREFIX/man]
+ --datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
+ --datadir=DIR read-only architecture-independent data [DATAROOTDIR]
+ --infodir=DIR info documentation [DATAROOTDIR/info]
+ --localedir=DIR locale-dependent data [DATAROOTDIR/locale]
+ --mandir=DIR man documentation [DATAROOTDIR/man]
+ --docdir=DIR documentation root [DATAROOTDIR/doc/autotoolset]
+ --htmldir=DIR html documentation [DOCDIR]
+ --dvidir=DIR dvi documentation [DOCDIR]
+ --pdfdir=DIR pdf documentation [DOCDIR]
+ --psdir=DIR ps documentation [DOCDIR]
_ACEOF
cat <<\_ACEOF
@@ -869,8 +1289,8 @@
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
- CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
- headers in a nonstandard directory <include dir>
+ CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
+ you have headers in a nonstandard directory <include dir>
EMACS the Emacs editor command
EMACSLOADPATH
the Emacs library search path
@@ -881,120 +1301,86 @@
Report bugs to <Marcelo Roberto Jimenez <mro...@ce...>>.
_ACEOF
+ac_status=$?
fi
if test "$ac_init_help" = "recursive"; then
# If there are subdirs, report their specific --help.
- ac_popdir=`pwd`
for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
- test -d $ac_dir || continue
+ test -d "$ac_dir" || continue
ac_builddir=.
-if test "$ac_dir" != .; then
+case "$ac_dir" in
+.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
+*)
ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
- # A "../" for each directory in $ac_dir_suffix.
- ac_top_builddir=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,../,g'`
-else
- ac_dir_suffix= ac_top_builddir=
-fi
+ # A ".." for each directory in $ac_dir_suffix.
+ ac_top_builddir_sub=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,/..,g;s,/,,'`
+ case $ac_top_builddir_sub in
+ "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
+ *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
+ esac ;;
+esac
+ac_abs_top_builddir=$ac_pwd
+ac_abs_builddir=$ac_pwd$ac_dir_suffix
+# for backward compatibility:
+ac_top_builddir=$ac_top_build_prefix
case $srcdir in
- .) # No --srcdir option. We are building in place.
+ .) # We are building in place.
ac_srcdir=.
- if test -z "$ac_top_builddir"; then
- ac_top_srcdir=.
- else
- ac_top_srcdir=`echo $ac_top_builddir | sed 's,/$,,'`
- fi ;;
- [\\/]* | ?:[\\/]* ) # Absolute path.
+ ac_top_srcdir=$ac_top_builddir_sub
+ ac_abs_top_srcdir=$ac_pwd ;;
+ [\\/]* | ?:[\\/]* ) # Absolute name.
ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir ;;
- *) # Relative path.
- ac_srcdir=$ac_top_builddir$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_builddir$srcdir ;;
+ ac_top_srcdir=$srcdir
+ ac_abs_top_srcdir=$srcdir ;;
+ *) # Relative name.
+ ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
+ ac_top_srcdir=$ac_top_build_prefix$srcdir
+ ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
esac
+ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-# Do not use `cd foo && pwd` to compute absolute paths, because
-# the directories may not exist.
-case `pwd` in
-.) ac_abs_builddir="$ac_dir";;
-*)
- case "$ac_dir" in
- .) ac_abs_builddir=`pwd`;;
- [\\/]* | ?:[\\/]* ) ac_abs_builddir="$ac_dir";;
- *) ac_abs_builddir=`pwd`/"$ac_dir";;
- esac;;
-esac
-case $ac_abs_builddir in
-.) ac_abs_top_builddir=${ac_top_builddir}.;;
-*)
- case ${ac_top_builddir}. in
- .) ac_abs_top_builddir=$ac_abs_builddir;;
- [\\/]* | ?:[\\/]* ) ac_abs_top_builddir=${ac_top_builddir}.;;
- *) ac_abs_top_builddir=$ac_abs_builddir/${ac_top_builddir}.;;
- esac;;
-esac
-case $ac_abs_builddir in
-.) ac_abs_srcdir=$ac_srcdir;;
-*)
- case $ac_srcdir in
- .) ac_abs_srcdir=$ac_abs_builddir;;
- [\\/]* | ?:[\\/]* ) ac_abs_srcdir=$ac_srcdir;;
- *) ac_abs_srcdir=$ac_abs_builddir/$ac_srcdir;;
- esac;;
-esac
-case $ac_abs_builddir in
-.) ac_abs_top_srcdir=$ac_top_srcdir;;
-*)
- case $ac_top_srcdir in
- .) ac_abs_top_srcdir=$ac_abs_builddir;;
- [\\/]* | ?:[\\/]* ) ac_abs_top_srcdir=$ac_top_srcdir;;
- *) ac_abs_top_srcdir=$ac_abs_builddir/$ac_top_srcdir;;
- esac;;
-esac
-
- cd $ac_dir
- # Check for guested configure; otherwise get Cygnus style configure.
- if test -f $ac_srcdir/configure.gnu; then
- echo
- $SHELL $ac_srcdir/configure.gnu --help=recursive
- elif test -f $ac_srcdir/configure; then
- echo
- $SHELL $ac_srcdir/configure --help=recursive
- elif test -f $ac_srcdir/configure.ac ||
- test -f $ac_srcdir/configure.in; then
- echo
- $ac_configure --help
+ cd "$ac_dir" || { ac_status=$?; continue; }
+ # Check for guested configure.
+ if test -f "$ac_srcdir/configure.gnu"; then
+ echo &&
+ $SHELL "$ac_srcdir/configure.gnu" --help=recursive
+ elif test -f "$ac_srcdir/configure"; then
+ echo &&
+ $SHELL "$ac_srcdir/configure" --help=recursive
else
echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
- fi
- cd $ac_popdir
+ fi || ac_status=$?
+ cd "$ac_pwd" || { ac_status=$?; break; }
done
fi
-test -n "$ac_init_help" && exit 0
+test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
GNU autotoolset configure 0.11.5
-generated by GNU Autoconf 2.59
+generated by GNU Autoconf 2.60
-Copyright (C) 2003 Free Software Foundation, Inc.
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
+2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
This configure script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
_ACEOF
- exit 0
+ exit
fi
-exec 5>config.log
-cat >&5 <<_ACEOF
+cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by GNU autotoolset $as_me 0.11.5, which was
-generated by GNU Autoconf 2.59. Invocation command line was
+generated by GNU Autoconf 2.60. Invocation command line was
$ $0 $@
_ACEOF
+exec 5>>config.log
{
cat <<_ASUNAME
## --------- ##
@@ -1013,7 +1399,7 @@
/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
-hostinfo = `(hostinfo) 2>/dev/null || echo unknown`
+/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
@@ -1027,6 +1413,7 @@
test -z "$as_dir" && as_dir=.
echo "PATH: $as_dir"
done
+IFS=$as_save_IFS
} >&5
@@ -1048,7 +1435,6 @@
ac_configure_args=
ac_configure_args0=
ac_configure_args1=
-ac_sep=
ac_must_keep_next=false
for ac_pass in 1 2
do
@@ -1059,7 +1445,7 @@
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
continue ;;
- *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
+ *\'*)
ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
esac
case $ac_pass in
@@ -1081,9 +1467,7 @@
-* ) ac_must_keep_next=true ;;
esac
fi
- ac_configure_args="$ac_configure_args$ac_sep'$ac_arg'"
- # Get rid of the leading space.
- ac_sep=" "
+ ac_configure_args="$ac_configure_args '$ac_arg'"
;;
esac
done
@@ -1094,8 +1478,8 @@
# When interrupted or exit'd, cleanup temporary files, and complete
# config.log. We remove comments because anyway the quotes in there
# would cause problems or look ugly.
-# WARNING: Be sure not to use single quotes in there, as some shells,
-# such as our DU 5.0 friend, will then `close' the trap.
+# WARNING: Use '\'' to represent an apostrophe within the trap.
+# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
trap 'exit_status=$?
# Save into config.log some information that might help in debugging.
{
@@ -1108,20 +1492,34 @@
_ASBOX
echo
# The following way of writing the cache mishandles newlines in values,
-{
+(
+ for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
+ eval ac_val=\$$ac_var
+ case $ac_val in #(
+ *${as_nl}*)
+ case $ac_var in #(
+ *_cv_*) { echo "$as_me:$LINENO: WARNING: Cache variable $ac_var contains a newline." >&5
+echo "$as_me: WARNING: Cache variable $ac_var contains a newline." >&2;} ;;
+ esac
+ case $ac_var in #(
+ _ | IFS | as_nl) ;; #(
+ *) $as_unset $ac_var ;;
+ esac ;;
+ esac
+ done
(set) 2>&1 |
- case `(ac_space='"'"' '"'"'; set | grep ac_space) 2>&1` in
- *ac_space=\ *)
+ case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
+ *${as_nl}ac_space=\ *)
sed -n \
- "s/'"'"'/'"'"'\\\\'"'"''"'"'/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='"'"'\\2'"'"'/p"
- ;;
+ "s/'\''/'\''\\\\'\'''\''/g;
+ s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
+ ;; #(
*)
- sed -n \
- "s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
+ sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
- esac;
-}
+ esac |
+ sort
+)
echo
cat <<\_ASBOX
@@ -1132,22 +1530,28 @@
echo
for ac_var in $ac_subst_vars
do
- eval ac_val=$`echo $ac_var`
- echo "$ac_var='"'"'$ac_val'"'"'"
+ eval ac_val=\$$ac_var
+ case $ac_val in
+ *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
+ esac
+ echo "$ac_var='\''$ac_val'\''"
done | sort
echo
if test -n "$ac_subst_files"; then
cat <<\_ASBOX
-## ------------- ##
-## Output files. ##
-## ------------- ##
+## ------------------- ##
+## File substitutions. ##
+## ------------------- ##
_ASBOX
echo
for ac_var in $ac_subst_files
do
- eval ac_val=$`echo $ac_var`
- echo "$ac_var='"'"'$ac_val'"'"'"
+ eval ac_val=\$$ac_var
+ case $ac_val in
+ *\'\''*) ac_val=`echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
+ esac
+ echo "$ac_var='\''$ac_val'\''"
done | sort
echo
fi
@@ -1159,26 +1563,24 @@
## ----------- ##
_ASBOX
echo
- sed "/^$/d" confdefs.h | sort
+ cat confdefs.h
echo
fi
test "$ac_signal" != 0 &&
echo "$as_me: caught signal $ac_signal"
echo "$as_me: exit $exit_status"
} >&5
- rm -f core *.core &&
- rm -rf conftest* confdefs* conf$$* $ac_clean_files &&
+ rm -f core *.core core.conftest.* &&
+ rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
exit $exit_status
- ' 0
+' 0
for ac_signal in 1 2 13 15; do
trap 'ac_signal='$ac_signal'; { (exit 1); exit 1; }' $ac_signal
done
ac_signal=0
# confdefs.h avoids OS command line length limits that DEFS can exceed.
-rm -rf conftest* confdefs.h
-# AIX cpp loses on an empty file, so make sure it contains at least a newline.
-echo >confdefs.h
+rm -f -r conftest* confdefs.h
# Predefined preprocessor variables.
@@ -1209,14 +1611,17 @@
# Let the site file select an alternate cache file if it wants to.
# Prefer explicitly selected file to automatically selected ones.
-if test -z "$CONFIG_SITE"; then
- if test "x$prefix" != xNONE; then
- CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
- else
- CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
- fi
+if test -n "$CONFIG_SITE"; then
+ set x "$CONFIG_SITE"
+elif test "x$prefix" != xNONE; then
+ set x "$prefix/share/config.site" "$prefix/etc/config.site"
+else
+ set x "$ac_default_prefix/share/config.site" \
+ "$ac_default_prefix/etc/config.site"
fi
-for ac_site_file in $CONFIG_SITE; do
+shift
+for ac_site_file
+do
if test -r "$ac_site_file"; then
{ echo "$as_me:$LINENO: loading site script $ac_site_file" >&5
echo "$as_me: loading site script $ac_site_file" >&6;}
@@ -1232,8 +1637,8 @@
{ echo "$as_me:$LINENO: loading cache $cache_file" >&5
echo "$as_me: loading cache $cache_file" >&6;}
case $cache_file in
- [\\/]* | ?:[\\/]* ) . $cache_file;;
- *) . ./$cache_file;;
+ [\\/]* | ?:[\\/]* ) . "$cache_file";;
+ *) . "./$cache_file";;
esac
fi
else
@@ -1245,12 +1650,11 @@
# Check that the precious variables saved in the cache have kept the same
# value.
ac_cache_corrupted=false
-for ac_var in `(set) 2>&1 |
- sed -n 's/^ac_env_\([a-zA-Z_0-9]*\)_set=.*/\1/p'`; do
+for ac_var in $ac_precious_vars; do
eval ac_old_set=\$ac_cv_env_${ac_var}_set
eval ac_new_set=\$ac_env_${ac_var}_set
- eval ac_old_val="\$ac_cv_env_${ac_var}_value"
- eval ac_new_val="\$ac_env_${ac_var}_value"
+ eval ac_old_val=\$ac_cv_env_${ac_var}_value
+ eval ac_new_val=\$ac_env_${ac_var}_value
case $ac_old_set,$ac_new_set in
set,)
{ echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
@@ -1275,8 +1679,7 @@
# Pass precious variables to config.status.
if test "$ac_new_set" = set; then
case $ac_new_val in
- *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
- ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
+ *\'*) ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
*) ac_arg=$ac_var=$ac_new_val ;;
esac
case " $ac_configure_args " in
@@ -1293,11 +1696,6 @@
{ (exit 1); exit 1; }; }
fi
-ac_ext=c
-ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
@@ -1322,35 +1720,46 @@
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+am__api_version="1.9"
ac_aux_dir=
-for ac_dir in config $srcdir/config; do
- if test -f $ac_dir/install-sh; then
+for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do
+ if test -f "$ac_dir/install-sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install-sh -c"
break
- elif test -f $ac_dir/install.sh; then
+ elif test -f "$ac_dir/install.sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install.sh -c"
break
- elif test -f $ac_dir/shtool; then
+ elif test -f "$ac_dir/shtool"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/shtool install -c"
break
fi
done
if test -z "$ac_aux_dir"; then
- { { echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in config $srcdir/config" >&5
-echo "$as_me: error: cannot find install-sh or install.sh in config $srcdir/config" >&2;}
+ { { echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&5
+echo "$as_me: error: cannot find install-sh or install.sh in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" >&2;}
{ (exit 1); exit 1; }; }
fi
-ac_config_guess="$SHELL $ac_aux_dir/config.guess"
-ac_config_sub="$SHELL $ac_aux_dir/config.sub"
-ac_configure="$SHELL $ac_aux_dir/configure" # This should be Cygnus configure.
-am__api_version="1.9"
+# These three variables are undocumented and unsupported,
+# and are intended to be withdrawn in a future Autoconf release.
+# They can cause serious problems if a builder's source tree is in a directory
+# whose full name contains unusual characters.
+ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
+ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
+ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
+
+
# Find a good install program. We prefer a C program (faster),
# so one script is as good as another. But avoid the broken or
# incompatible versions:
@@ -1364,8 +1773,8 @@
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
# OS/2's system install, which has a completely different semantic
# ./install, which can be erroneously created by make from ./install.sh.
-echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5
-echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6
+{ echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5
+echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6; }
if test -z "$INSTALL"; then
if test "${ac_cv_path_install+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
@@ -1387,7 +1796,7 @@
# by default.
for ac_prog in ginstall scoinst install; do
for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then
+ if { test -f "$as_dir/$ac_prog$ac_exec_ext" && $as_executable_p "$as_dir/$ac_prog$ac_exec_ext"; }; then
if test $ac_prog = install &&
grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# AIX install. It has an incompatible calling convention.
@@ -1406,21 +1815,22 @@
;;
esac
done
+IFS=$as_save_IFS
fi
if test "${ac_cv_path_install+set}" = set; then
INSTALL=$ac_cv_path_install
else
- # As a last resort, use the slow shell script. We don't cache a
- # path for INSTALL within a source directory, because that will
+ # As a last resort, use the slow shell script. Don't cache a
+ # value for INSTALL within a source directory, because that will
# break other packages using the cache if that directory is
- # removed, or if the path is relative.
+ # removed, or if the value is a relative name.
INSTALL=$ac_install_sh
fi
fi
-echo "$as_me:$LINENO: result: $INSTALL" >&5
-echo "${ECHO_T}$INSTALL" >&6
+{ echo "$as_me:$LINENO: result: $INSTALL" >&5
+echo "${ECHO_T}$INSTALL" >&6; }
# Use test -z because SunOS4 sh mishandles braces in ${var-val}.
# It thinks the first close brace ends the variable substitution.
@@ -1430,8 +1840,8 @@
test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
-echo "$as_me:$LINENO: checking whether build environment is sane" >&5
-echo $ECHO_N "checking whether build environment is sane... $ECHO_C" >&6
+{ echo "$as_me:$LINENO: checking whether build environment is sane" >&5
+echo $ECHO_N "checking whether build environment is sane... $ECHO_C" >&6; }
# Just in case
sleep 1
echo timestamp > conftest.file
@@ -1473,20 +1883,20 @@
Check your system clock" >&2;}
{ (exit 1); exit 1; }; }
fi
-echo "$as_me:$LINENO: result: yes" >&5
-echo "${ECHO_T}yes" >&6
+{ echo "$as_me:$LINENO: result: yes" >&5
+echo "${ECHO_T}yes" >&6; }
test "$program_prefix" != NONE &&
- program_transform_name="s,^,$program_prefix,;$program_transform_name"
+ program_transform_name="s&^&$program_prefix&;$program_transform_name"
# Use a double $ so make ignores it.
test "$program_suffix" != NONE &&
- program_transform_name="s,\$,$program_suffix,;$program_transform_name"
+ program_transform_name="s&\$&$program_suffix&;$program_transform_name"
# Double any \ or $. echo might interpret backslashes.
# By default was `s,x,x', remove it if useless.
cat <<\_ACEOF >conftest.sed
s/[\\$]/&&/g;s/;s,x,x,$//
_ACEOF
program_transform_name=`echo $program_transform_name | sed -f conftest.sed`
-rm conftest.sed
+rm -f conftest.sed
# expand $ac_aux_dir to an absolute path
am_aux_dir=`cd $ac_aux_dir && pwd`
@@ -1538,8 +1948,8 @@
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
-echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+{ echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; }
if test "${ac_cv_prog_AWK+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
@@ -1552,54 +1962,57 @@
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; }; then
ac_cv_prog_AWK="$ac_prog"
echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
+IFS=$as_save_IFS
fi
fi
AWK=$ac_cv_prog_AWK
if test -n "$AWK"; then
- echo "$as_me:$LINENO: result: $AWK" >&5
-echo "${ECHO_T}$AWK" >&6
+ { echo "$as_me:$LINENO: result: $AWK" >&5
+echo "${ECHO_T}$AWK" >&6; }
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ { echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6; }
fi
+
test -n "$AWK" && break
done
-echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5
-echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6
-set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y,:./+-,___p_,'`
-if eval "test \"\${ac_cv_prog_make_${ac_make}_set+set}\" = set"; then
+{ echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5
+echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6; }
+set x ${MAKE-make}; ac_make=`echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'`
+if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
cat >conftest.make <<\_ACEOF
+SHELL = /bin/sh
all:
- @echo 'ac_maketemp="$(MAKE)"'
+ @echo '@@@%%%=$(MAKE)=@@@%%%'
_ACEOF
# GNU make sometimes prints "make[1]: Entering...", which would confuse us.
-eval `${MAKE-make} -f conftest.make 2>/dev/null | grep temp=`
-if test -n "$ac_maketemp"; then
- eval ac_cv_prog_make_${ac_make}_set=yes
-else
- eval ac_cv_prog_make_${ac_make}_set=no
-fi
+case `${MAKE-make} -f conftest.make 2>/dev/null` in
+ *@@@%%%=?*=@@@%%%*)
+ eval ac_cv_prog_make_${ac_make}_set=yes;;
+ *)
+ eval ac_cv_prog_make_${ac_make}_set=no;;
+esac
rm -f conftest.make
fi
-if eval "test \"`echo '$ac_cv_prog_make_'${ac_make}_set`\" = yes"; then
- echo "$as_me:$LINENO: result: yes" >&5
-echo "${ECHO_T}yes" >&6
+if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
+ { echo "$as_me:$LINENO: result: yes" >&5
+echo "${ECHO_T}yes" >&6; }
SET_MAKE=
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ { echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6; }
SET_MAKE="MAKE=${MAKE-make}"
fi
@@ -1670,8 +2083,8 @@
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args.
set dummy ${ac_tool_prefix}strip; ac_word=$2
-echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+{ echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; }
if test "${ac_cv_prog_STRIP+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
@@ -1684,32 +2097,34 @@
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; }; then
ac_cv_prog_STRIP="${ac_tool_prefix}strip"
echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
+IFS=$as_save_IFS
fi
fi
STRIP=$ac_cv_prog_STRIP
if test -n "$STRIP"; then
- echo "$as_me:$LINENO: result: $STRIP" >&5
-echo "${ECHO_T}$STRIP" >&6
+ { echo "$as_me:$LINENO: result: $STRIP" >&5
+echo "${ECHO_T}$STRIP" >&6; }
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ { echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6; }
fi
+
fi
if test -z "$ac_cv_prog_STRIP"; then
ac_ct_STRIP=$STRIP
# Extract the first word of "strip", so it can be a program name with args.
set dummy strip; ac_word=$2
-echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+{ echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6; }
if test "${ac_cv_prog_ac_ct_STRIP+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
@@ -1722,27 +2137,41 @@
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; }; then
ac_cv_prog_ac_ct_STRIP="strip"
echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
+IFS=$as_save_IFS
- test -z "$ac_cv_prog_ac_ct_STRIP" && ac_cv_prog_ac_ct_STRIP=":"
fi
fi
ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP
if test -n "$ac_ct_STRIP"; then
- echo "$as_me:$LINENO: result: $ac_ct_STRIP" >&5
-echo "${ECHO_T}$ac_ct_STRIP" >&6
+ { echo "$as_me:$LINENO: result: $ac_ct_STRIP" >&5
+echo "${ECHO_T}$ac_ct_STRIP" >&6; }
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ { echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6; }
fi
- STRIP=$ac_ct_STRIP
+ if test "x$ac_ct_STRIP" = x; then
+ STRIP=":"
+ else
+ case $cross_compiling:$ac_tool_warned in
+yes:)
+{ echo "$as_me:$LINENO: WARNING: In the future, Autoconf will not detect cross-tools
+whose name does not start with the host triplet. If you think this
+configuration is useful to you, please write to aut...@gn...." >&5
+echo "$as_...
[truncated message content] |
|
From: <mro...@us...> - 2007-05-14 00:53:57
|
Revision: 37
http://autotoolset.svn.sourceforge.net/autotoolset/?rev=37&view=rev
Author: mroberto
Date: 2007-05-13 17:53:59 -0700 (Sun, 13 May 2007)
Log Message:
-----------
* using_automake_autoconf.texi, fortran.texi, gnu_build_system.texi,
good_code.texi, legal.texi, installing_gnu_software.texi,
philosophy.texi, using_autotools.texi, makefiles.texi, gnu_emacs.texi,
preface.texi: Several corrections by Jens Rantil
<jen...@te...>.
Modified Paths:
--------------
trunk/ChangeLog
trunk/THANKS
trunk/doc/tutorial/fortran.texi
trunk/doc/tutorial/gnu_build_system.texi
trunk/doc/tutorial/gnu_emacs.texi
trunk/doc/tutorial/good_code.texi
trunk/doc/tutorial/installing_gnu_software.texi
trunk/doc/tutorial/legal.texi
trunk/doc/tutorial/makefiles.texi
trunk/doc/tutorial/philosophy.texi
trunk/doc/tutorial/preface.texi
trunk/doc/tutorial/using_automake_autoconf.texi
trunk/doc/tutorial/using_autotools.texi
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/ChangeLog 2007-05-14 00:53:59 UTC (rev 37)
@@ -1,3 +1,11 @@
+2007-05-13 Marcelo Roberto Jimenez <mro...@ce...>
+
+ * using_automake_autoconf.texi, fortran.texi, gnu_build_system.texi,
+ good_code.texi, legal.texi, installing_gnu_software.texi,
+ philosophy.texi, using_autotools.texi, makefiles.texi, gnu_emacs.texi,
+ preface.texi: Several corrections by Jens Rantil
+ <jen...@te...>.
+
2003-06-10 Marcelo Roberto Jimenez <mro...@ce...>
* misc/autotoolset.spec.in (Packager): removed % sign from the
Modified: trunk/THANKS
===================================================================
--- trunk/THANKS 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/THANKS 2007-05-14 00:53:59 UTC (rev 37)
@@ -5,12 +5,14 @@
suggesting various improvements, or submitting actual code. Here is
a list of these people. Help me keep it complete and exempt of errors.
-John Eaton <jw...@be...>
-Francois Pinard <pi...@ir...>
-Richard Stallman <rm...@gn...>
??? (The guy that wrote f2c) <dm...@be...>
-Trent Fisher <tr...@cs...>
-Lionel Cons <Lio...@ce...>
Dennis Barbier <ba...@ch...>
+Francois Pinard <pi...@ir...>
+Jens Rantil <jen...@te...>
+John Eaton <jw...@be...>
Karl Dalley <ba...@ed...>
+Lionel Cons <Lio...@ce...>
+Marcelo Roberto Jimenez <mro...@ce...>
Nathan Myers <nc...@ca...>
+Richard Stallman <rm...@gn...>
+Trent Fisher <tr...@cs...>
Modified: trunk/doc/tutorial/fortran.texi
===================================================================
--- trunk/doc/tutorial/fortran.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/fortran.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -28,7 +28,7 @@
@menu
* Introduction to Fortran support::
* Fortran compilers and linkage::
-* Walkthrough a simple example::
+* Walk through a simple example::
* The gory details::
* Portability problems with Fortran::
* Other Fortran dialects::
@@ -75,7 +75,7 @@
@c =========================================================================
-@node Fortran compilers and linkage, Walkthrough a simple example, Introduction to Fortran support, Using Fortran effectively
+@node Fortran compilers and linkage, Walk through a simple example, Introduction to Fortran support, Using Fortran effectively
@section Fortran compilers and linkage
The traditional Hello world program in Fortran looks like this:
@@ -129,7 +129,7 @@
@noindent
This is the analog of a @samp{void} function in C, because it takes
arguments but doesn't return anything. The prototype declaration is
-@dfn{K&R} style: you list all the arguments in parenthesis, seperated with
+@dfn{K&R} style: you list all the arguments in parenthesis, separated with
commas, and you declare the types of the variables in the subsequent lines.
Suppose that this subroutine is saved as @file{fhello.f}. To call it from
@@ -161,7 +161,7 @@
compiler. Unfortunately, linkage in Fortran is not standard, and there
exist compilers that handle strings differently. For example, some compilers
will prepend the string with a few bytes containing the length and pass
-a pointer to the whole thing. This problem is not limitted to strings.
+a pointer to the whole thing. This problem is not limited to strings.
It happens in many other instances.
The @samp{f2c} and @samp{g77} compilers follow compatible linkage, and
we will use this linkage as the @emph{ad-hoc standard}. A few proprietary
@@ -215,7 +215,7 @@
These are all defined in a header file called @samp{f2c.h} which you are
supposed to include in your source code before declaring any prototypes.
We will show you how this is all done in the next section. The following
-table showes the types that are most likely to interest you. For more info,
+table shows the types that are most likely to interest you. For more info,
take a look at the @samp{f2c.h} file itself:
@example
integer -> int
@@ -262,8 +262,8 @@
@c ==========================================================================
-@node Walkthrough a simple example, The gory details, Fortran compilers and linkage, Using Fortran effectively
-@section Walkthrough a simple example
+@node Walk through a simple example, The gory details, Fortran compilers and linkage, Using Fortran effectively
+@section Walk through a simple example
Now that we have brought up some of the issues about Fortran linkage, let's
show you how to work around them. We will write a simple Fortran function,
@@ -466,7 +466,7 @@
@noindent
It may seem an overkill to carry around a Fortran compiler. On the other hand
you will find it very convenient, and the @samp{f2c} compiler isn't really
-that big. If you are spoiled on a system that is well equiped and with a good
+that big. If you are spoiled on a system that is well equipped and with a good
system administrator, you may find it a nasty surprise one day when you
discover that the rest of the world is not necessarily like that.
@@ -484,7 +484,7 @@
@c =========================================================================
-@node The gory details, Portability problems with Fortran, Walkthrough a simple example, Using Fortran effectively
+@node The gory details, Portability problems with Fortran, Walk through a simple example, Using Fortran effectively
@section The gory details
The best way to get started is by building the initial directory tree with
@@ -536,7 +536,7 @@
Define if the compiler uses uppercase for symbol names.
@end table
These macros are used to define @samp{f77func} macro which takes two arguments;
-the name of the Fortan subroutine or function in lower case, and then in
+the name of the Fortran subroutine or function in lower case, and then in
upper case, and returns the correct symbol name to use for invoking it from
C or C++. To obtain the calling sequence for the symbol do:
@example
@@ -588,7 +588,7 @@
@noindent
both on the toplevel directory level.
@item
-Add the following macro invokations in the middle of @file{configure.in}, in
+Add the following macro invocations in the middle of @file{configure.in}, in
this order:
@example
AC_PROG_CC
@@ -601,7 +601,7 @@
If you have invoked @code{LF_CONFIGURE_CC} then there is no need to
invoke @code{AC_PROG_CC} again.
@item
-Add the following invokation just before @code{AC_OUTPUT}:
+Add the following invocation just before @code{AC_OUTPUT}:
@example
AC_CONFIG_SUBDIRS([fortran/f2c fortran/libf2c])
@end example
@@ -758,7 +758,7 @@
even though @emph{there are no free compilers} for both variants,
they are becoming alarmingly popular with the scientific community.
In fact, I think that the main reason why these variants of Fortran are
-being developed is to make more bussiness for proprietary compiler
+being developed is to make more business for proprietary compiler
developers. So far as I know, Fortran 90 does not provide any features
that C++ can not support with a class library extension. Moreover
Fortran 90 does not have the comprehensive foundation that allows C++ to be
@@ -807,7 +807,7 @@
but it is very rarely that you will ever want to go with single precision.
Occasionally, you may find that the programmer breaks the rules. For example,
in @code{fftpack} the array @code{IFAC} is supposed to be a @code{double}
-even though implicitly it is suggested to be an @code{int}. Such inconstances
+even though implicitly it is suggested to be an @code{int}. Such inconstancies
will probably show up in compiler errors. To fix them, declare the type
of these variables explicitly. If it's an array then you do it like this:
@example
@@ -899,7 +899,7 @@
@noindent
Please don't contribute to the spread of these dialects. Instead contribute
infrastructure to better languages, like C and C++, to support the features
-that compell you to use Fortran 90 or HPF.
+that compel you to use Fortran 90 or HPF.
@c ----------------------------------------------------------------------------
Modified: trunk/doc/tutorial/gnu_build_system.texi
===================================================================
--- trunk/doc/tutorial/gnu_build_system.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/gnu_build_system.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -67,9 +67,9 @@
makefile standards, taking away the extraordinary effort required to produce
them by hand. Automake requires Autoconf in order to be used properly.
@item
-@strong{Libtool} makes it possible to compile position indepedent code and
+@strong{Libtool} makes it possible to compile position independent code and
build shared libraries in a portable manner. It does not require either
-Autoconf, or Automake and can be used indepedently. Automake however supports
+Autoconf, or Automake and can be used independently. Automake however supports
libtool and interoperates with it in a seamless manner.
@item
@strong{Autotoolset} helps you develop portable source code that conforms
@@ -169,7 +169,7 @@
You will need the GNU versions of @code{make}, @code{m4} and
@code{tar} even if your system already has native versions of these utilities.
To check whether you do have the GNU versions see whether they accept the
-@code{--version} flag. If you have proprietory versions of @code{make} or
+@code{--version} flag. If you have proprietary versions of @code{make} or
@code{m4}, rename them and then install the GNU ones.
You will also need to install @emph{Perl}, the @emph{GNU C compiler},
and the @emph{TeX} typesetting system. These programs are always installed
@@ -532,14 +532,14 @@
@item
The @samp{autoconf} command combines the @file{aclocal.m4} and
@file{configure.in} files and produces the @file{configure} script.
-And now we are in bussiness.
+And now we are in business.
@item
The @samp{touch} command makes the files @file{README} and friends exist.
It is important that these files exist before calling Automake, because
Automake decides whether to include them in a distribution by checking
if they exist at the time that you invoke @samp{automake}. Automake
@emph{must} decide to include these files, because when you type
-@samp{make distcheck} the presense of these files will be required.
+@samp{make distcheck} the presence of these files will be required.
@item
The @samp{automake} command compiles a @file{Makefile.in} file from
@file{Makefile.am} and if absent it installs various files that are required
@@ -568,7 +568,7 @@
probing the installer platform. Each one of these substitutions consists
of a symbolic name, and the actual text that we want to substitute.
When the @file{configure} script runs @code{AC_OUTPUT} it parses
-all of the files listed in @code{AC_OUTPUT} and every occurance of
+all of the files listed in @code{AC_OUTPUT} and every occurence of
@code{@@FOO@@} in these files is substituted with the text that corresponds
to @code{FOO}. For example, if you add the following lines to
@file{configure.in} you will cause @code{@@FOO@@} to be substituted with
@@ -837,7 +837,7 @@
or ideas and suggestions do not require legal paper exchanges.
You can also decide to send some kind of special greeting when you
-initially add a name to your @file{THANKS} file. The mere presense
+initially add a name to your @file{THANKS} file. The mere presence
of a name in @file{THANKS} is then a flag to you that the initial
greeting has been sent.
@item
@@ -859,7 +859,7 @@
The @emph{GNU coding standards} explain in a lot of detail how you should
structure a @file{ChangeLog}, so you should read about it there.
-The basic idea is to record @emph{semi-permenant modifications} you make to
+The basic idea is to record @emph{semi-permanant modifications} you make to
your source code. It is not necessary to continuously record changes
that you make while you are experimenting with something. But once you
decide that you got a modification worked out, then you should record
@@ -868,7 +868,7 @@
This way, it will be possible to tell what changes happened between
versions.
-You can automate @file{ChangeLog} maintainance with emacs.
+You can automate @file{ChangeLog} maintenance with emacs.
@xref{Navigating source code}, for more details.
Recently versions of Emacs use
the ISO 8601 standard for dates which is: @code{YYYY-MM-DD} (year-month-date).
@@ -912,7 +912,7 @@
(@pxref{Hello world example with Autoconf and Automake}).
Such packages are called @dfn{shallow}.
-In general, it is prefered to organize your package as a @dfn{deep package}.
+In general, it is preferred to organize your package as a @dfn{deep package}.
In a deep package, the documentation files
@example
README, INSTALL, AUTHORS, THANKS, ChangeLog, COPYING
@@ -927,9 +927,9 @@
should have it's own subdirectory. Executables should get their own
directory as well. If each executable corresponds only to one or two files
then it is sensible to put them all under the same directory. If your
-executables need more source files, or they can be seperated in distinct
+executables need more source files, or they can be separated in distinct
classes of functionalities you may like to regroup them under multiple
-directories. Feel free to use your judgement on how to do this best.
+directories. Feel free to use your judgment on how to do this best.
It is easiest to place the library test suites on the same directory with
the library source code. If that does not sit well with you however, you
should put the test suite for each library in subdirectories @emph{under} that
@@ -939,7 +939,7 @@
An optional directory where you put portability-related source code.
This is mainly replacement implementation for system calls that
are unavailable on some systems. You can also put tools here that you commonly
-use accross many different packages, tools that are too simple to just
+use across many different packages, tools that are too simple to just
make libraries out of every one of them. Common files encountered here
are files that replace system calls to the GNU C library that are not
available in proprietary C libraries.
@@ -947,7 +947,7 @@
A directory containing the documentation for your package.
You have the creative freedom to present the documentation in any way that is
effective. However
-the prefered way to document software is by using Texinfo. Texinfo has the
+the preferred way to document software is by using Texinfo. Texinfo has the
advantage that you can produce both on-line help as well as nice printed
books from the same source. Documentation is discussed in more detail
in @xref{Maintaining Documentation}.
@@ -956,17 +956,17 @@
@emph{install}.
These files define new @samp{autoconf} macros that you
should make available to other developers who want to use your libraries.
-This is discussed in more detail in @strong{FIXME: crossreference}.
+This is discussed in more detail in @strong{FIXME: cross reference}.
@item intl
A directory containing boilerplate portability source code that allows
your program to speak in many human languages. The contents of this
directory are automatically maintained by @samp{gettext}.
-(@strong{FIXME: crossreference})
+(@strong{FIXME: cross reference})
@item po
A directory containing message catalogs for your software package.
This is where the maintainer places the translations of per software
in multiple human languages.
-(@strong{FIXME: crossreference})
+(@strong{FIXME: cross reference})
@end table
Automake makes it very easy to maintain multidirectory source code
packages, so you shouldn't shy away from taking advantage of it.
@@ -1199,7 +1199,7 @@
out @samp{AC_PROG_CXX} if you don't plan to use C++. You can edit and
customize this file to your needs. More specifically, you will need to
update the version number in @samp{AM_INIT_AUTOMAKE}
-everytime you cut a new distribution (@pxref{Handling version numbers}).
+every time you cut a new distribution (@pxref{Handling version numbers}).
You should also make sure to list all the subdirectories that have
a @file{Makefile.am} in @samp{AC_OUTPUT}.
@item
Modified: trunk/doc/tutorial/gnu_emacs.texi
===================================================================
--- trunk/doc/tutorial/gnu_emacs.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/gnu_emacs.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -35,7 +35,7 @@
because it provides an integrated environment for software development.
The simplest thing you can do with Emacs is edit your source code.
However, you can do a lot more than that. You can run a debugger,
-and step through your program while Emacs showes you the corresponding
+and step through your program while Emacs shows you the corresponding
sources that you are stepping through. You can browse on-line Info
documentation and man pages, download and read your email off-line, and
follow discussions on newsgroups. Emacs is particularly helpful with writing
@@ -86,7 +86,7 @@
a sophisticated xterm, and an understanding psychotherapist.
Under the X window system, Emacs controls multiple x-windows
-called @dfn{frames}. Each frame has a menubar and the main editing area.
+called @dfn{frames}. Each frame has a menu bar and the main editing area.
The editing area is divided into @dfn{windows} with horizontal bars.
You can grab these bars and move them around with the first mouse button.
@footnote{Note that in Emacs parlance a @dfn{window} is not an X window.
@@ -102,7 +102,7 @@
the windows that you have on your screen.
A buffer can be @dfn{visiting} files. In that case, the contents of the
-buffer reflect the contents of a file that is being editted. But buffers
+buffer reflect the contents of a file that is being edited. But buffers
can be associated with anything you like, so long as you program
it up. For example, under the Dired directory editor, a buffer is bound
to a directory, showing you the contents of the directory. When you
@@ -113,8 +113,8 @@
simply rebinds the existing buffer for that file.
Emacs uses a variant of LISP, called Emacs LISP, as its programming language.
-Everytime you press a key, click the mouse, or select an entry from the
-menubar, an Emacs LISP function is evaluated. The @dfn{mode} of the
+Every time you press a key, click the mouse, or select an entry from the
+menu bar, an Emacs LISP function is evaluated. The @dfn{mode} of the
buffer determines, among many other things, what function to evaluate.
This way, every buffer can be associated with functionality that defines
what you do in that buffer. For example you can program your buffer to edit
@@ -211,7 +211,7 @@
code distribution and compile it yourself. Installing Emacs is not
difficult. If Emacs is already installed on your GNU/Linux system,
you might still need to reinstall it: you might not have the most
-recent version, you might have Xemacs instead, you might not have
+recent version, you might have XEmacs instead, you might not have
support for internationalization, or your Emacs might not have compiled
support for reading mail over POP (a feature very useful to developers
that hook up over modem). If any of these is the case, then uninstall
@@ -229,7 +229,7 @@
@item intlfonts-@value{intlfonts}.tar.gz
This file contains the fonts that Emacs uses to support international
languages. If you want international language support, you will
-definetely need this.
+definitely need this.
@end table
Get a copy of these three files, place them under the same directory
and unpack them with the following commands:
@@ -314,7 +314,7 @@
@c FIXME: describe minibuffer and what the other mouse-buttons do
Under the X window system, Emacs controls multiple x-windows which are
-called @dfn{franes}. Each frame has a menubar and the main editing area.
+called @dfn{frames}. Each frame has a menu bar and the main editing area.
The editing area is divided into @dfn{windows}
@c --
@footnote{Note that in Emacs lingo a @dfn{window} does not correspond
@@ -341,7 +341,7 @@
the windows that you actually have on your screen.
A buffer can be @dfn{visiting} files. In that case, the contents of the
-buffer reflect the contents of a file that is being editted. But buffers
+buffer reflect the contents of a file that is being edited. But buffers
can be associated with anything you like, so long as you program
it up. For example, under the Dired directory editor, a buffer is bound
to a directory, showing you the contents of the directory. When you
@@ -376,7 +376,7 @@
Help @expansion{} Emacs Tutorial
@end example
@noindent
-If you are a vi user, or you simply prefer to use `vi' keybindings, then
+If you are a vi user, or you simply prefer to use `vi' key bindings, then
read @ref{Using vi emulation}.
In Emacs, every @dfn{event} causes a Lisp function to be executed.
@@ -411,8 +411,8 @@
These functions can also be aborted with @kbd{C-g}.
It is standard in Emacs documentation to refer to the @key{ALT} key with
-the letter @samp{M}. So, in the future, we will be refering to function
-invokations as:
+the letter @samp{M}. So, in the future, we will be referring to function
+invocations as:
@example
M-x @var{function-name}
@end example
@@ -485,7 +485,7 @@
In general I favor dark backgrounds and @samp{fixed} fonts. Dark backgrounds
make it easier to sit in front of the monitor for a prolonged period of
time. @samp{fixed} fonts looks nice and it's small enough to make efficient
-use of your screenspace. Some people might prefer larger fonts however.
+use of your screen space. Some people might prefer larger fonts however.
When Emacs starts up, it looks for a file called @file{.emacs} at the user's
home directory, and evaluates it's contents through the Emacs Lisp
@@ -596,7 +596,7 @@
@item
You can write your own modes! If you write a program whose use involves
editing some type of input files, it is very much appreciated by the
-community if you also write an Emacs mode for thet file and distribute
+community if you also write an Emacs mode for that file and distribute
it with your program.
@end enumerate
@@ -645,7 +645,7 @@
will select text and mouse button 2 will paste it. Unfortunately,
when you click mouse button 2, emacs will first move the cursor at the
location of the mouse, and then insert the text in that location.
-If you are used to editing with vi under xterms, you will instead prefer
+If you are used to editing with vi under xterm, you will instead prefer
to position the cursor yourself, and use mouse button 2 to simply cause
the text to be pasted without changing the position of the cursor. If you
prefer this behaviour, then add the following line to your @file{.emacs}:
@@ -656,7 +656,7 @@
However, you can also select and paste into an Emacs buffer text that
you select from other applications, like your web browser, or your xterm.
@item
-Use @dfn{font-lock}. Font-lock decorates your editted text with colors that
+Use @dfn{font-lock}. Font-lock decorates your edited text with colors that
make it easier to read text with complicated syntax, such as software
source codes. This is one of the coolest features of Emacs. To use it, add
the following lines to your @file{.emacs}:
@@ -703,7 +703,7 @@
@noindent
Note the use of @samp{expand-file-name} for dealing with non-absolute
directories. If you are a user in an account where you don't have root
-priviledge, you are very likely to need to install your Emacs packages
+privilege, you are very likely to need to install your Emacs packages
in a non-standard directory.
@item
@xref{Using vi emulation}, if you would like to customize Emacs to run
@@ -762,7 +762,7 @@
and more comfortable.
@end itemize
Because most rearrangements of finger habits are not as optimal as the
-vi finger habits, most vi users react very unpleasently to other editors.
+vi finger habits, most vi users react very unpleasantly to other editors.
For the benefit of these users, in this section we describe how to
run a vi editor under the Emacs system. Similarly, users of other editors
find the vi finger habits strange and unintuitive. For the benefit of
@@ -822,7 +822,7 @@
@item
@dfn{Insert mode}:
When you are in insert mode, the editor simply @dfn{inserts} the things that
-you type into the text that is being editted. If there are any characters
+you type into the text that is being edited. If there are any characters
in front of your cursor, these characters are pushed ahead and they are
not overwritten. Under Viper, when you are in insert mode, the color
of your cursor is green. The only key that has special meaning, while you
@@ -855,7 +855,7 @@
You want to be in that mode to access the intended functionality. Occasionally
however, you may like to hop to viper's command mode to navigate the buffer,
do a search or save the buffer's contents. When you hop to one of the
-other three modes, the buffer will suddendly be just text to your editor.
+other three modes, the buffer will suddenly be just text to your editor.
@end itemize
While you are in Command mode, you can prepend keystrokes with a number.
Then the subsequent keystroke will be executed as many times as the number.
@@ -965,11 +965,11 @@
@item /@var{string} <RET>
Search for @var{string}.
@item n
-Go to the next occurance of @var{string}.
+Go to the next occurence of @var{string}.
@item N
-Go to the previous occurance of @var{string}.
+Go to the previous occurence of @var{string}.
@item :%s/@var{string1}/@var{string2}/g <RET>
-Replace all occurances of @var{string1} with @var{string2}.
+Replace all occurences of @var{string1} with @var{string2}.
Use this with extreme caution!
@end table
@item
@@ -1059,10 +1059,10 @@
filename rather than navigate your way there through the directory editor.
To go down a directory, move the cursor over the directory filename and
-press enter. To go up a few directories, press @kbd{f1} and when you
+press @kbd{RET}. To go up a few directories, press @kbd{f1} and when you
are prompted for the new directory, with the current directory as the
default choice, erase your way up the hierarchy and press @key{RET}.
-To take a jump to a substantially different directort that you have
+To jump to a substantially different directory that you have
visited recently, press @kbd{f1} and then when prompted for the destination
directory name, use the cursor keys to select the directory that you want
among the list of directories that you have recently visited.
@@ -1102,7 +1102,7 @@
you note that it is calling another function @code{gleep}. If you move
your cursor on @code{gleep}, then Emacs will let you jump to the file
where @code{gleep} is defined by pressing @kbd{M-.}. You can also jump to
-other occurances in your code where @code{gleep} is invoked by pressing
+other occurences in your code where @code{gleep} is invoked by pressing
@kbd{M-,}. In order for this
to work, you need to do two things: you need to generate a tags
file, and you need to tell emacs to load the file. If your source code
@@ -1113,7 +1113,7 @@
@end example
@noindent
from the top-level directory of your source tree. Then load the tags
-file in Emacs by navigating Dired to the toplevel directory of your
+file in Emacs by navigating Dired to the top-level directory of your
source code, and pressing @kbd{f6}.
While editing a file, you may want to hop to the shell prompt to run a
@@ -1130,7 +1130,7 @@
when the tar file is not compressed. Usually tar files are distributed
compressed, so you should uncompress them first with @kbd{Z} before
entering them. Also, be careful not to load an extremely huge tar file.
-Emacs may mean ``eating memory and constantly swaping'' to some people, but
+Emacs may mean ``eating memory and constantly swapping'' to some people, but
don't push it!
Another very powerful feature of Emacs is the Ange-FTP package: it allows
@@ -1196,7 +1196,7 @@
@c Explain about GNUS and RMAIL.
@c How to configure RMAIL
@c Running RMAIL
-@c keybindings for sending/reading mail
+@c key bindings for sending/reading mail
@c all about labeling mail. advice on what labels are nice to use
@c saving mail to other files
@c replying to spam
@@ -1349,7 +1349,7 @@
write the body of the current message to a file
@end table
@noindent
-Other than browing email, here is some things that you will want to do:
+Other than browsing email, here is some things that you will want to do:
@itemize @bullet
@item
@strong{Compose a message}: To compose a message press @kbd{m}. Emacs
@@ -1398,7 +1398,7 @@
@item To:
list address of the recipient to whom the message is directed
@item Cc:
-list addresses of other recipients that need to recieve courtesy copies
+list addresses of other recipients that need to receive courtesy copies
of the message
@item BCC:
list addresses of other recipients to send a copy to, without showing their
@@ -1478,9 +1478,9 @@
Every once in a while, after long heroic efforts in front of the computer
monitor, a software developer will need to some counseling to feel
-better about perself. In RL (real life) counseling is very expensive and
+better about herself. In RL (real life) counseling is very expensive and
it also involves getting up from your computer and transporting yourself
-to another location, which descreases your productivity. Emacs can help you.
+to another location, which decreases your productivity. Emacs can help you.
Run @code{M-x doctor}, and you will talk to a psychiatrist for free.
Many people say that hackers work too hard and they should go out for
@@ -1564,7 +1564,7 @@
(@file{widget.dvi})
@item RefTeX User Manual
If you are writing large documents with LaTeX that contain a lot of
-crossreferences, then the RefTeX package will make your life easier.
+cross references, then the RefTeX package will make your life easier.
(@file{reftex.dvi})
@item Ediff User's Manual
Ediff is a comprehensive package for dealing with patches under Emacs.
Modified: trunk/doc/tutorial/good_code.texi
===================================================================
--- trunk/doc/tutorial/good_code.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/good_code.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -39,7 +39,7 @@
When you work on a software project, one of your short-term goals is to
solve a problem at hand. If you are doing this because someone asked you
to solve the problem, then all you need to do to look good in per eyes is to
-deliver a program that works. Nevetheless, regardless of how little
+deliver a program that works. Nevertheless, regardless of how little
person may appreciate this, doing just that is not good enough.
Once you have code that gives the right answer to a specific set of problems,
you will want to make improvements to it. As you make these improvements,
@@ -94,12 +94,12 @@
One of the disadvantages of C++ is that C++ object files compiled by
different C++ compilers can not be linked together.
In order to compile C++ to machine language, a lot of compilation issues
-need to be defered to the linking stage. Because object file formats
+need to be deferred to the linking stage. Because object file formats
are not traditionally sophisticated enough to handle these issues, C++
compilers do various ugly kludges. The problem is that different compilers
-do these kludges differently, making object files accross compilers
+do these kludges differently, making object files across compilers
incompatible. This is not a terrible problem, since object files are
-incompatible accross different platforms anyways. It is only a problem
+incompatible across different platforms anyways. It is only a problem
when you want to use more than one compiler on the same platform.
Another disadvantage of C++ is that it is harder
to interface a C++ library to another language, than it is to interface
@@ -138,7 +138,7 @@
integer arithmetic and floating point arithmetic. The simplicity of
Scheme syntax, and the completeness of Guile, make it very easy to
implement specialized scripting languages simply by translating them to
-Scheme. In Scheme algorithms and data are interchangable. As a result,
+Scheme. In Scheme algorithms and data are interchangeable. As a result,
it is easy to write Scheme programs that manipulate Scheme source code.
This makes Scheme an ideal language for writing programs that manipulate
algorithms instead of data, such as programs that do symbolic algebra.
@@ -152,7 +152,7 @@
computational core of scientific applications. We do have free compilers
for Fortran 77, so using it does not restrict our freedom.
(@pxref{Using Fortran effectively})
-Also, Fortran 77 is an aggresively optimizable language, and this makes it
+Also, Fortran 77 is an aggressively optimized language, and this makes it
very attractive to engineers that want to write code optimized for speed.
Unfortunately,
Fortran 77 can not do well @emph{anything} except array-oriented
@@ -192,7 +192,7 @@
@noindent
It is almost impossible to write good programs entirely in Fortran, so
please use Fortran only for the numerical core of your application
-and do the bookeeping tasks, including input/output using a more appropriate
+and do the bookkeeping tasks, including input/output using a more appropriate
language.
If you have written a program entirely in Fortran, please do not ask anyone
@@ -201,12 +201,12 @@
at least C and C++ and use Fortran only when necessary. Please do not
hold the opinion that contributions in science and engineering
are ``true'' contributions and software development is just a ``tool''.
-This bigotted attitude is behind the thousands of lines of ugly unmaintainable
+This bigoted attitude is behind the thousands of lines of ugly unmaintainable
code that goes around in many places. Good software development can be
an important contribution in its own right, and regardless of what your
goals are, please appreciate it and encourage it. To maximize the benefits
of good software, please make your software free.
-(@strong{FIXME: Crossreference copyright section in this chapter})
+(@strong{FIXME: Cross reference copyright section in this chapter})
@c --------------------------------------------------------------------------
@@ -215,14 +215,14 @@
The key to better code is to focus away from developing
monolithic throw-away hacks that do only one job, and focus on developing
-@dfn{libraries} (@strong{FIXME: crossreference}). Break down the original
+@dfn{libraries} (@strong{FIXME: cross reference}). Break down the original
problem to parts, and the parts to smaller parts, until you get down to simple
subproblems that can be easily tested, and from which you can construct
solutions for both the original problem and future variants. Every library
that you write is a legacy that you can share with other developers, that
want to solve similar problems. Each library will allow these other developers
to focus on their problem and not have to reinvent the parts that are common
-with your work from scratch. You should definetely make libraries out of
+with your work from scratch. You should definitely make libraries out of
subproblems that are likely to be broadly useful.
Please be very liberal in what you consider ``broadly useful''.
Please program in a defensive way that renders reusable as much code as
@@ -262,7 +262,7 @@
#endif
@end example
@noindent
-This way it becomes easy to switch them on or off upon demand. The prefered
+This way it becomes easy to switch them on or off upon demand. The preferred
way to manipulate a macro like this @code{INSPECT_ERRORS} is by adding
a switch to your @file{configure} script. You can do this by adding the
following lines to @file{configure.in}:
@@ -287,9 +287,9 @@
it is easy to think that you are producing work with every new line of code
that is written. The reality is that you @emph{know} you have produced new
work
-everytime you write working a test program for new features, and
+every time you write working a test program for new features, and
@emph{not a minute before}.
-Another time when you should definetely write a test program is when you
+Another time when you should definitely write a test program is when you
find a bug while ordinarily using the library. Then, write a test program
that triggers the bug, fix the bug, and keep the test in your test suite.
This way, if a future modification reintroduces the same bug it will be
@@ -303,7 +303,7 @@
obligations bugging you around for your attention. There may be times that
you have to stay away from a project for a large amount of time.
If you have consistently been maintaining documentation, it will help you
-refocus on your project even after many months of absense.
+refocus on your project even after many months of absence.
@node Developing applications, Free software is good software, Developing libraries, Writing Good Programs
@section Developing applications
@@ -360,7 +360,7 @@
the application is used. Applications should also recognize the
@code{--version} switch and state their version number. The easiest
way to make applications understand these two switches is to use the
-GNU Argp library (@emph{FIXME: crossreference}).
+GNU Argp library (@emph{FIXME: cross reference}).
@c --------------------------------------------------------------------------
@@ -439,7 +439,7 @@
@end example
@noindent
@item
-For a shells script (bash, perl) that uses hash marks for commenting,
+For a shells script (BASH, Perl) that uses hash marks for commenting,
create the standard notice with
@example
% gpl -sh foo.pl
@@ -540,7 +540,7 @@
are distributed as part of a build system.
@item gpl-m4
Insert the standard GPL copyright notice using m4 commenting (i.e. dnl)
-and the special Autoconf exception. This is the prefered notice for new
+and the special Autoconf exception. This is the preferred notice for new
Autoconf macros.
@item gpl-el
Insert the standard GPL copyright notice using Elisp commenting. This
Modified: trunk/doc/tutorial/installing_gnu_software.texi
===================================================================
--- trunk/doc/tutorial/installing_gnu_software.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/installing_gnu_software.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -155,7 +155,7 @@
The @dfn{GNU coding standards} are a document that describes the requirements
that must be satisfied by all GNU programs. These requirements are driven
-mainly by technical ocnsiderations, and they are excellent advice for
+mainly by technical considerations, and they are excellent advice for
writing good software. The @dfn{makefile standards}, a part of the
GNU coding standards, require that your
makefiles do a lot more than simply compile and install the software.
@@ -193,7 +193,7 @@
% make uninstall
@end example
@noindent
-from the toplevel directory of the source distribution. This will work only
+from the top level directory of the source distribution. This will work only
if the source distribution is configured first. It will work best only
if you do it from the same source distribution, with the same configuration,
that you've used to install the package in the first place.
@@ -201,7 +201,7 @@
When you install GNU software, archive the source code to all the packages
that you install in a directory like @file{/usr/src} or @file{/usr/local/src}.
To do that, first run @code{make clean} on the source distribution, and then
-use a recursive copy to copy it to @file{/usr/src}. The presense of a
+use a recursive copy to copy it to @file{/usr/src}. The presence of a
source distribution in one of these directories should be a signal to you
that the corresponding package is currently installed.
@@ -286,7 +286,7 @@
The @file{/usr/local} directory is called the @dfn{prefix}. The default
prefix is always @file{/usr/local} but you can set it to anything you like
when you call @samp{configure} by adding a @samp{--prefix} option.
-For example, suppose that you are not a privilidged user, so you can not
+For example, suppose that you are not a privileged user, so you can not
install anything in @file{/usr/local}, but you would still like to install
the package for your own use. Then you can tell the @samp{configure}
script to install the package in your home directory
@@ -375,7 +375,7 @@
@end example
@noindent
This assumes that you are using the @code{bash} shell as your default shell.
-If you use the @code{csh} or @code{tcsh} shellls, you need to assign
+If you use the @code{csh} or @code{tcsh} shells, you need to assign
environment variables with the @code{setenv} command instead. For example:
@example
% setenv CFLAGS "-O3"
@@ -422,7 +422,7 @@
@noindent
The configure script and the generated makefiles will take care of the rest.
-vpath builds are prefered by some people for the following reasons:
+vpath builds are preferred by some people for the following reasons:
@enumerate
@item
They prevent the build process form cluttering your source directory
Modified: trunk/doc/tutorial/legal.texi
===================================================================
--- trunk/doc/tutorial/legal.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/legal.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -118,7 +118,7 @@
The law is less clear about what happens if person refers to your work
without actually doing any copying. A judge will have to decide this if it
goes to court. This is why when you work on a free software project,
-the only way to avoid liabilities like this is by not refering to anyone
+the only way to avoid liabilities like this is by not referring to anyone
else's work, unless per work is also free software. This is one of the many
ways that copyright obstructs cooperation between citizens.
@@ -156,7 +156,7 @@
patented in the future. What makes it insane is that the patent office,
in its infinite stupidity, has patented algorithms that are very trivial
with nothing innovative about them. For example, the use of
-@dfn{backing store} in a multiprocesing window system, like X11, is
+@dfn{backing store} in a multiprocessing window system, like X11, is
covered by patent 4,555,775. In the spring of 1991, the owner of the
patent, AT&T, threatened to sue every member of the X Consortium including
MIT. Backing store is the idea that the windowing system save the contents of
@@ -177,9 +177,9 @@
It is not necessary for someone to have a solid case
to get you into trouble. The cost of litigation is often sufficient extortion
-to force small bussinesses, non-profit organizations and individual software
+to force small businesses, non-profit organizations and individual software
developers to settle, even when there is not solid case. The only defense
-against a patent attac is to prove that there is ``prior art''; in other
+against a patent attack is to prove that there is ``prior art''; in other
words, you need to show that what is described in the patent had already
been invented before the date on which the application for that patent was
filed. Unfortunately, this is costly, not guaranteed to work, and
@@ -195,9 +195,9 @@
extort some cash.
There have actually been patent attacks aimed directly against the free
-sofwtare community. The GNU system does not include the Unix @samp{compress}
+software community. The GNU system does not include the Unix @samp{compress}
utility because it infringes a patent, and the patent owner has specifically
-targetted the volunteer that wrote a @samp{compress} program for the
+targeted the volunteer that wrote a @samp{compress} program for the
GNU project.
There may be more patent attacks in the future.
On November of 1998 two
@@ -207,7 +207,7 @@
It is important to note however that when an algorithm is patented,
and, worse, when that patent is asserted by the owner, this is an
attack on @emph{everyone} that writes software, not only to the free
-software community. This is why it is not important who is being targetted
+software community. This is why it is not important who is being targeted
in each specific incident. Patents hurt all of us.
@c ----------------------------------------------------------------------------
@@ -261,7 +261,7 @@
Encryption is routinely used now by human rights activists operating on
totalitarian countries. Encryption can also be used to create an
unsanctioned para-economy based on digital cash, and allow individuals
-to carry out transcations and contracts completely anonymously.
+to carry out transactions and contracts completely anonymously.
These prospects are not good news for Big Brother.
The Free Software Foundation is fighting the US government export
@@ -306,7 +306,7 @@
to make a free version proprietary. This measure is called
@dfn{copyleft} because it subverts the copyright law to do the opposite of
what copyright is normally used for (i.e. to prevent a user to make a
-proprietary package free). The GNU GPL does not oblidge you to distribute
+proprietary package free). The GNU GPL does not oblige you to distribute
your modifications. It only requires that you distribute them freely,
@emph{if} you choose to distribute them at all. The decision of whether
or not to distribute your derived work is entirely up to you.
@@ -346,7 +346,7 @@
The GNU GPL is a legal instrument that has been
designed to create a
safe haven in which software can be written free from copyright law
-encumberence. It allows developers to freely share their work with
+encumbrance. It allows developers to freely share their work with
a friendly community that is also willing to share theirs, and at the
same time protect them from being exploited by publishers of proprietary
software. Many developers would not contribute to our community without
Modified: trunk/doc/tutorial/makefiles.texi
===================================================================
--- trunk/doc/tutorial/makefiles.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/makefiles.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -178,10 +178,10 @@
Object files @file{*.o} contain definitions of variables
and subroutines written out in @dfn{assembly}
-(machine language ``pseudocode''). Most of
+(machine language ``pseudo code''). Most of
these definitions will eventually be embedded in the final executable
program at a specific address. At this stage however these memory addresses
-are not known so they are being refered to symbolically. These
+are not known so they are being referred to symbolically. These
symbolic references are called @dfn{symbols}. It is possible to list
the symbols defined in an object file with the @samp{nm} command.
For example:
@@ -230,15 +230,15 @@
During the process of linking, all the machine language instructions that
refer to a specific memory address need to be modified to use the correct
-addresses within the executable, as oppposed to the addresses within their
+addresses within the executable, as opposed to the addresses within their
object file. This becomes an issue when you want to your program to load
and link compiled object files during run-time instead of compile-time.
To make such @dfn{dynamic linking} possible, your symbols need to be
@dfn{relocatable}. This means that your symbols definitions must be
correct no matter where you place them in memory. There should be no
memory addresses that need to be modified. One way to do this is by
-refering to memory addresses within the object file by giving an offset
-from the refering address. Memory addresses outside the object file must
+referring to memory addresses within the object file by giving an offset
+from the referring address. Memory addresses outside the object file must
be treated as @dfn{interlibrary dependencies} and you must tell the compiler
what you expect them to be when you attempt to build relocatable machine code.
Unfortunately some flavours of Unix do not handle interlibrary dependencies
@@ -290,7 +290,7 @@
The reason for this is historical. Originally @code{ar}
was meant to be used merely for packaging files together. The more
-well known program @code{tar} is a descendent of @code{ar} that was designed
+well known program @code{tar} is a descendant of @code{ar} that was designed
to handle making such archives on a tape device. Now that tape devices are
more or less obsolete, @code{tar} is playing the role that was originally
meant for @code{ar}. As for @code{ar}, way back, some people thought to
@@ -418,7 +418,7 @@
For portability, it is better that the @samp{-I} appear before the filenames
of the source files that we want to compile.
-A good coding standard is to distringuish private from public header files
+A good coding standard is to distinguish private from public header files
in your source code by including private header files like
@example
#include "private.h"
@@ -739,7 +739,7 @@
(recall that X is built on top of the sockets interface and it is essentially a
communications protocol between the computer running the program and
computer that controls the screen in which the X program is displayed.)
-@emph{FIXME: Crossreferences, if we explain all this in more details}.
+@emph{FIXME: Cross references, if we explain all this in more details}.
Because it is necessary to link system libraries to form an executable,
under copyright law, the executable is derived work from the system libraries.
@@ -820,7 +820,7 @@
@dfn{phony targets}.
@item
In general a @dfn{dependency} is a file that is used as input to create a
-target. If a target has more than one dependencies, they must be seperated
+target. If a target has more than one dependencies, they must be separated
by spaces, but they must remain on the same line. It is possible for
a target to have no dependencies. In that case, the space after the
semicolon must be left blank. It is also possible for a target, even
@@ -1171,7 +1171,7 @@
These problems are not impossible to deal with, but you need a lot of
experience in makefile writing to overcome them. Most developers don't
want to bother as much with all this, and would rather be debugging
-ther source code. The GNU build system helps you set up your source code
+their source code. The GNU build system helps you set up your source code
to make this possible. For the same example, the GNU developer only needs to
write the following @file{Makefile.am} file:
@example
Modified: trunk/doc/tutorial/philosophy.texi
===================================================================
--- trunk/doc/tutorial/philosophy.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/philosophy.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -450,7 +450,7 @@
purpose of copyright is to promote progress---not to
reward authors. Copyright does reward authors
somewhat, and publishers more, but that is intended as a
-means of modifying their behavior.
+means of modifying their behaviour.
The real established tradition of our society is that
copyright cuts into the natural rights of the
Modified: trunk/doc/tutorial/preface.texi
===================================================================
--- trunk/doc/tutorial/preface.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/preface.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -34,7 +34,7 @@
GNU coding standards.
-This manual introduces you to the GNU build system and showes you how
+This manual introduces you to the GNU build system and shows you how
to develop high-quality
This manual shows you how to develop high-quality software on GNU using
@@ -64,9 +64,9 @@
makefile standards, taking away the extraordinary effort required to produce
them by hand. Automake requires Autoconf in order to be used properly.
@item
-@strong{Libtool} makes it possible to compile position indepedent code and
+@strong{Libtool} makes it possible to compile position independent code and
build shared libraries in a portable manner. It does not require either
-Autoconf, or Automake and can be used indepedently. Automake however supports
+Autoconf, or Automake and can be used independently. Automake however supports
libtool and interoperates with it in a seamless manner.
@item
@strong{Autotoolset}
@@ -97,7 +97,7 @@
Some tasks that are simplified by the GNU build system include:
@itemize @bullet
@item
-Building multidirectory software packages. It is much more difficult to use
+Building multi directory software packages. It is much more difficult to use
raw @code{make} recursively. Having simplified this step, the developer
is encouraged to organize his source code in a deep directory tree rather than
lump everything under the same directory. Developers that use raw @code{make}
@@ -141,7 +141,7 @@
@item
Some rudimentary portability framework for C++ programs. There is a lot
of room for improvement here, in the future. Also a framework for
-embedding text into your executable and handling include files accross
+embedding text into your executable and handling include files across
multiple directories.
@item
Support for writing portable software that uses both Fortran and C++.
@@ -183,7 +183,7 @@
the manual that I haven't written or haven't yet developed fully, please
contact me.
-Chapters 1,2,3,4 are okey. Chapter 5 is okey to, but needs a little more
+Chapters 1,2,3,4 are okay. Chapter 5 is okay to, but needs a little more
work. I removed the other chapters to minimize confusion, but the sources
for them are still being distributed as part of the Autotoolset package
for those that found them useful. The other chapters need a lot of rewriting
@@ -191,5 +191,5 @@
Please contact me if you have any suggestions
for improving this manual.
-Remarks by Marcelo: I am currentrly updating this manual to the last release
+Remarks by Marcelo: I am currently updating this manual to the last release
of the autoconf/automake tools.
Modified: trunk/doc/tutorial/using_automake_autoconf.texi
===================================================================
--- trunk/doc/tutorial/using_automake_autoconf.texi 2007-04-05 13:02:21 UTC (rev 36)
+++ trunk/doc/tutorial/using_automake_autoconf.texi 2007-05-14 00:53:59 UTC (rev 37)
@@ -141,8 +141,8 @@
dir2/Makefile])
@end example
@noindent
-Do not put the ending parentesis in another line, separeted from the ending
-bracket, this will cause a misbehavior of the macro.
+Do not put the ending parenthesis in another line, separated from the ending
+bracket, this will cause a misbehaviour of the macro.
@end itemize
As we explained before to build this package you need to execute the following
@@ -203,14 +203,14 @@
@item
The @samp{autoconf} command combines the @file{aclocal.m4} and
@file{configure.ac} files and produces the @file{configure} script.
-And now we are in bussiness.
+And now we are in business.
@item
The @samp{touch} command makes the files @file{README} and friends exist.
It is important that these files exist before calling Automake, because
Automake decides whether to include them in a distribution by checking
if they exist at the time that you invoke @samp{automake}. Automake
@emph{must} decide to include these files, because when you type
-@samp{make distcheck} the presense of these files will be required.
+@samp{make distcheck} the presence of these files will be required.
@item
The @samp{automake} command compiles a @file{Makefile.in} file from
@file{Makefile.am} and if absent it installs various files that are required
@@ -241,7 +241,7 @@
distributed with Autotoolset is no longer needed, because the file
@file{acconfig.h} is no longer used by Autoconf/Automake. This section is
kept here only for historical reasons and may soon be removed or rewritten.
-Nevertheless, the description of the behavior of @samp{autoheader} has been
+Nevertheless, the description of the behaviour of @samp{autoheader} has been
updated and is correct. That said...
As you may have noticed, the @samp{configure} script in the previous example
@@ -361,7 +361,7 @@
distribution, and consequently didn't know how to deal with the
@code{PACKAGE} and @code{VERSION} macros. This problem is now solved with the
use of the new syntax of the macro AC_INIT. But we choose to keep
-this discussion here because (a) it is still usefull and (b) someone may
+this discussion here because (a) it is still useful and (b) someone may
be using the old syntax that was kept for compatibility or (c) you have old
versions of the @code{automake/autoconf} packages.
@@ -391,7 +391,7 @@
@end example
@noindent
At this point you would run @code{autoconf} again, so that it took into account
-the presense of @code{acconfig.h}:
+the presence of @code{acconfig.h}:
@example
% aclocal
% autoconf
@@ -474,8 +474,8 @@
then @samp{acconfig} will also install entries for these macros.
The @code{acconfig} program may be revised in the future and perhaps
it might be eliminated (note: indeed...). There is an unofficial patch to
-Autoconf that will automate the maintance of @file{acconfig.h}, eliminating
-the need for a seperate program. I am not yet certain if that patch will be
+Autoconf that will automate the maintenance of @file{acconfig.h}, eliminating
+the need for a separate program. I am not yet certain if that patch will be
part of the official next version of Autoconf, but I very much expect it
to (note: I think it has been included). Until then, if you are interested, see:
@code{http://www.clark.net/pub/dickey/autoconf/autoconf.html}
@@ -550,7 +550,7 @@
little theorems and use the little theorems to hide the complexity in
proving bigger theorems, in software engineering you develop libraries
to take care of low-level details once and for all so that they are
-out of the way everytime you make a different implementation for
+out of the way every time you make a different implementation for
a variation of the problem.
On a higher level you still don't create just
@@ -580,9 +580,9 @@
@emph{just do it!} I can not emphasize that enough. When you write new code
you have the illusion that you are producing work, only to find out tomorrow
that you need an entire week to debug it. As a rule, internalize the reality
-that you @emph{know} you have produced new work everytime you write a working
+that you @emph{know} you have produced new work every time you write a working
test program for the new features, and @emph{not a minute before}.
-Another time when you should definetly write a test suite is when you
+Another time when you should definitely write a test suite is when you
find a bug while ordinarily using the library. Then, before you even
fix the bug, write a test program that detects the bug. Then go fix it.
This way, as you add new features to your libraries you have insurance that
@@ -593,11 +593,11 @@
is right after you get a few new test programs working. You might feel that
you are too busy to write documentation, but the truth of the matter
is that you will @emph{always} be too busy. After long hours debugging
-these seg faults, think of it as a celebration of triumph to fire up the
+these segfaults, think of it as a celebration of triumph to fire up the
editor and document your brand-spanking new cool features.
Please make sure that
-computational code is completely seperated from I/O code so ...
[truncated message content] |
