GNU M4 1.4.16 macro processor
The format of the
m4 command is:
m4 [option...] [file...]
All options begin with ‘–’, or if long option names are used, with ‘—’.
The argument—is a marker to denote the end of options.
In other words, m4 -QPDfoo -d a -df is equivalent to m4 -Q -P -D foo -d -df -- ./a, although the latter form is considered canonical.继续阅读
GNU Libtool 2.4.2
There are several examples throughout this document. All assume the same environment: we want to build a library, libhello, in a generic way.
libhello could be a shared library, a static library, or both… whatever is available on the host system, as long as libtool has been ported to it.继续阅读
3 Getting a GNU Account
The directory ‘/gd/gnuorg’ mentioned throughout this document is available on the general GNU server, currently
fencepost.gnu.org. If you are the maintainer of a GNU package, you should have an account there. If you don’t have one already, http://www.gnu.org/software/README.accounts.html. You can also ask for accounts for people who significantly help you in working on the package.继续阅读
Source EN: http://www.gnu.org/software/autoconf/manual/autoconf.html(version 2.68)
CN: http://www.linuxforum.net/books/autoconf.html(version 2.13)
Edition 2.13, for Autoconf version 2.13
A physicist, an engineer, and a computer scientist were discussing the
nature of God. Surely a Physicist, said the physicist, because
early in the Creation, God made Light; and you know, Maxwell's equations,
the dual nature of electro-magnetic waves, the relativist consequences...
An Engineer!, said the engineer, because before making Light,
God split the Chaos into Land and Water; it takes a hell of
an engineer to handle that bigamount of mud, and orderly
separation of solids from liquids... The computer scientist
shouted: And the Chaos, where do you think it was coming from, hmm?
1 About the GNU Coding Standards
The GNU Hello program serves as an example of how to follow the GNU coding standards for a trivial program. http://www.gnu.org/software/hello/hello.html.继续阅读