source: trunk/essentials/sys-devel/m4/README

Last change on this file was 3090, checked in by bird, 18 years ago

m4 1.4.8

File size: 2.6 KB
Line 
1GNU `m4' is an implementation of the traditional Unix macro
2processor. It is mostly SVR4 compatible, although it has some
3extensions (for example, handling more than 9 positional parameters
4to macros). `m4' also has built-in functions for including files,
5running shell commands, doing arithmetic, etc. Autoconf needs GNU
6`m4' for generating `configure' scripts, but not for running them.
7
8GNU `m4' was originally written by Rene' Seindal, from Denmark.
9This release is considered stable.
10
11If GNU `m4' is meant to serve GNU `autoconf', beware that `m4'
12should be fully installed *prior to* configuring `autoconf' itself.
13Likewise, if you intend on hacking GNU `m4' from CVS, the bootstrap
14process requires that you first install a released copy of GNU `m4'.
15
16If you are just trying to build `m4' from a released tarball, you
17should not normally need to run `./bootstrap' or `autoreconf'; just go
18ahead and start with `./configure'. If you are trying to build `m4'
19from CVS, more information can be found in the CVS-only file HACKING.
20
21In the subdirectory `examples' you will find various m4 files, ranging
22from trivial test files to rather advanced macros. If you intend to
23use m4 seriously, you might find useful material down there.
24
25See file `BACKLOG' for a summary of pending mail and articles.
26See file `COPYING' for copying conditions.
27See file `INSTALL' for compilation and installation instructions.
28See file `NEWS' for a list of major changes in the current release.
29See file `THANKS' for a list of contributors.
30
31By using `./configure --enable-changeword', you get an experimental
32feature which allows for changing the syntax of what is a "word" in
33`m4'. This feature will not be present in m4 2.0, but will be
34replaced by other new features which provide similar capability, so
35do not count on it.
36
37Send bug reports to `bug-m4@gnu.org'. A bug report is an adequate
38description of the problem: your input, what you expected, what you got,
39and why this is wrong. Diffs are welcome, but they only describe a
40solution, from which the problem might be uneasy to infer.
41
42========================================================================
43
44Copyright (C) 2000, 2005, 2006 Free Software Foundation, Inc.
45
46Permission is granted to copy, distribute and/or modify this document
47under the terms of the GNU Free Documentation License, Version 1.2 or
48any later version published by the Free Software Foundation; with no
49Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
50Texts. A copy of the license is included in the ``GNU Free
51Documentation License'' file as part of this distribution.
Note: See TracBrowser for help on using the repository browser.