Re: automake --no-force (Was: autoreconf invode automake with --no-force (autoconf ver.2.54))

[Nishio Futoshi]

At Tue, 01 Oct 2002 08:47:57 -0700,
Russ Allbery wrote:
> It's not too bad of a way to start, but it has a drawback that I've seen
> in probably the majority of Autoconf scripts out there, namely it creates
> a configure.in that checks for a bunch of things for which the source code
> has no workarounds or fallbacks.

O.K.  My tutorial needs next step.

If your Autotool scripts work, look at configure.in.  There are some
macros, as you have seen.  If you find unknown macros, please read
Info for Autoconf.  It's a good document for portability.  When you
write one macro in `configure.in', please read document for the macro.

Coping from configure.in to configure.in is very dangerous, because
many configure.in's were writen for old version (like 2.13). To copy,
you must check whether it is obsolute or not, by reading Info.


Well, autoconf Info file is up-to-date.  I want to express my thanks
for that document and author.