RE: Help: Missing something simple...

["Masterson, David" <David.Masterson@kla-tencor.com>]

Tried that -- no change.  By the way:

* Autoconf turns configure.in into configure.
* Autoconf does not turn Makefile.in into Makefile -- configure does.
* Automake turns Makefile.am into Makefile.in (does it do anything to
configure?).
* Therefore, assuming configure looks for aclocal.m4, the order of autoconf
and automake should probably not make a difference.

-----Original Message-----
From: gary@oranda.demon.co.uk [mailto:gary@oranda.demon.co.uk]
Sent: Thursday, May 20, 1999 12:25 AM
To: Masterson, David
Cc: 'automake@gnu.org'
Subject: Re: Help: Missing something simple...


"Masterson, David" <David.Masterson@kla-tencor.com> writes:

> Starting from a fresh directory (ie. no configure / Makefile /
Makefile.in),
> to generate the Makefile for this, I do:
> 
> 	$ aclocal
> 	$ autoconf
> 	$ automake -a
> 	$ configure --prefix=$TARGET
> 
> Examining the Makefile after this, I find that none of the Automake
> variables were properly expanded (particularly @PACKAGE@ and @VERSION@ --
in
> fact, all uppercase variables).  What am I missing?

autoconf turns ``Makefile.in'' into ``Makefile'' and automake turns
``Makefile.am'' into ``Makefile.in''.  You only start with a
``Makefile.am'',
ergo you must run "automake -a" *before* "autoconf".

Cheers,
        Gary.
-- 
  ___              _   ___   __              _
mailto:gary@oranda.demon.co.uk
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___
gary@gnu.org
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page:  /___/                      /___/                pgp-2 public
key:
http://www.oranda.demon.co.uk
http://www.oranda.demon.co.uk/pgp