mirror of
git://git.sv.gnu.org/autoconf
synced 2024-11-21 01:01:48 +08:00
* README: Recommend GNU M4 1.4.3 or later.
* doc/autoconf.texi (Introduction): Likewise. Reword to avoid some formatting glitches. Use "#!/bin/sh", not "#! /bin/sh"; the space isn't needed these days. Clarify explanation of HP compiler bug. Redo example output tp match current CVS snapshot. Use @example.org in email addresses when the examples might get inadvertently cut-and-pasted into user code. Remove example of autom4te usage that doesn't seem to work now. Use modern AC_INIT (except when the example is meant to be shown with Autoconf 2.13). Update ksh info for Solaris 9 and later. KB -> kB. Modernize description of Automake versions a bit. Don't claim a future version of Autoconf is near. Add [] to examples, so that the manual follows its own advice about quoting better. * doc/install.texi: Reword to avoid some formatting glitches.
This commit is contained in:
parent
bc31277f07
commit
2fa1c5c37e
28
ChangeLog
28
ChangeLog
@ -1,3 +1,29 @@
|
||||
2005-06-07 Paul Eggert <eggert@cs.ucla.edu>
|
||||
|
||||
* README: Recommend GNU M4 1.4.3 or later.
|
||||
* doc/autoconf.texi (Introduction): Likewise.
|
||||
Reword to avoid some formatting glitches.
|
||||
Use "#!/bin/sh", not "#! /bin/sh"; the space isn't needed these days.
|
||||
Clarify explanation of HP compiler bug.
|
||||
Redo example output tp match current CVS snapshot.
|
||||
Use @example.org in email addresses when the examples
|
||||
might get inadvertently cut-and-pasted into user code.
|
||||
Remove example of autom4te usage that doesn't seem to work now.
|
||||
Use modern AC_INIT (except when the example is meant to be
|
||||
shown with Autoconf 2.13).
|
||||
Update ksh info for Solaris 9 and later.
|
||||
KB -> kB.
|
||||
Modernize description of Automake versions a bit.
|
||||
Don't claim a future version of Autoconf is near.
|
||||
* doc/install.texi: Reword to avoid some formatting glitches.
|
||||
|
||||
2005-06-07 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
|
||||
|
||||
* doc/autoconf.texi: Add [] to examples, so that the manual
|
||||
follows its own advice about quoting better.
|
||||
Reword to avoid some formatting glitches.
|
||||
* doc/installt.exi: Reword to avoid some formatting glitches.
|
||||
|
||||
2005-06-06 Stepan Kasal <kasal@ucw.cz>
|
||||
|
||||
m4_cdr of one-member list was [[]] (one-member list containing an
|
||||
@ -23,7 +49,7 @@
|
||||
|
||||
* doc/autoconf.texi (Limitations of Usual Tools): Solaris' awk cannot
|
||||
swallow records with more than 99 fields.
|
||||
* lib/autotest/general.m4 (AT_INIT): Use the awk builtin `split' to
|
||||
* lib/autotest/general.m4 (AT_INIT): Use the awk builtin `split' to
|
||||
parse the long line.
|
||||
|
||||
2005-06-04 Stepan Kasal <kasal@ucw.cz>
|
||||
|
15
README
15
README
@ -11,18 +11,15 @@ operating system features that the package can use, in the form of M4
|
||||
macro calls.
|
||||
|
||||
Producing configuration scripts using Autoconf requires GNU M4 and
|
||||
Perl. You must install GNU M4 (version 1.4 or later) and Perl (5.005_03
|
||||
Perl. You must install GNU M4 (version 1.4.3 or later) and Perl (5.005_03
|
||||
or later) before configuring Autoconf, so that Autoconf's configure
|
||||
script can find them. The configuration scripts produced by Autoconf
|
||||
are self-contained, so their users do not need to have Autoconf (or
|
||||
GNU M4, Perl etc.).
|
||||
GNU M4, Perl, etc.).
|
||||
|
||||
Vanilla GNU m4 1.4 has some serious bugs, so we recommend using m4 1.4
|
||||
as patched by the standard GNU/Linux distributions. If you're
|
||||
building GNU m4 1.4 from scratch we suggest using 1.4.2 or later.
|
||||
You can get 1.4.2 here:
|
||||
You can get GNU M4 1.4.3 here:
|
||||
|
||||
ftp://ftp.gnu.org/gnu/m4/m4-1.4.2.tar.gz
|
||||
ftp://ftp.gnu.org/gnu/m4/m4-1.4.3.tar.gz
|
||||
|
||||
The file INSTALL should be distributed with packages that use
|
||||
Autoconf-generated configure scripts and Makefiles that conform to the
|
||||
@ -43,8 +40,8 @@ similarly for the other mailing lists.
|
||||
|
||||
-----
|
||||
|
||||
Copyright (C) 1992, 1993, 1994, 1998, 2000, 2001, 2002, 2003, 2004
|
||||
Free Software Foundation, Inc.
|
||||
Copyright (C) 1992, 1993, 1994, 1998, 2000, 2001, 2002, 2003, 2004,
|
||||
2005 Free Software Foundation, Inc.
|
||||
|
||||
This file is part of GNU Autoconf.
|
||||
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -120,16 +120,17 @@ before reconfiguring for another architecture.
|
||||
@node Installation Names
|
||||
@section Installation Names
|
||||
|
||||
By default, @samp{make install} will install the package's files in
|
||||
@file{/usr/local/bin}, @file{/usr/local/man}, etc. You can specify an
|
||||
By default, @samp{make install} installs the package's commands under
|
||||
@file{/usr/local/bin}, include files under @file{/usr/local/include}, etc.
|
||||
You can specify an
|
||||
installation prefix other than @file{/usr/local} by giving
|
||||
@command{configure} the option @option{--prefix=@var{prefix}}.
|
||||
|
||||
You can specify separate installation prefixes for architecture-specific
|
||||
files and architecture-independent files. If you give
|
||||
@command{configure} the option @option{--exec-prefix=@var{prefix}}, the
|
||||
package will use @var{prefix} as the prefix for installing programs and
|
||||
libraries. Documentation and other data files will still use the
|
||||
files and architecture-independent files. If you pass the option
|
||||
@option{--exec-prefix=@var{prefix}} to @command{configure}, the
|
||||
package uses @var{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
|
||||
@ -187,7 +188,7 @@ If @file{config.sub} isn't included in this package, then this package
|
||||
doesn't need to know the machine type.
|
||||
|
||||
If you are @emph{building} compiler tools for cross-compiling, you
|
||||
should use the @option{--target=@var{type}} option to select the type of
|
||||
should use the option @option{--target=@var{type}} to select the type of
|
||||
system they will produce code for.
|
||||
|
||||
If you want to @emph{use} a cross compiler, that generates code for a
|
||||
|
Loading…
Reference in New Issue
Block a user