Thank you for the (very!) prompt and helpful replies.
I don't know, of course, what you might have in mind regarding your
comment, "We ought to do something about this." However, as a first step,
I would respectfully suggest that any such ordering dependencies (at least
any that become known as "a classic gotcha"!) be noted wherever the macro
is described in the documentation.
As a possible alternative starting point: Is there a canonical list of
macros that must precede AM_INIT_AUTOMAKE? How about those that must
precede AC_PROG_LIBTOOL? Are there any general rules to follow (beyond
those that autoheader imposes)?
In any event, my immediate problem is now solved. Thanks again.
- WEB
----- Original Message -----
From: "Alexandre Duret-Lutz" <[EMAIL PROTECTED]>
To: "Walter E. Brown" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 02, 2003 12:42 PM
Subject: Re: autoreconf behavior
| >>> "Walter" == Walter E Brown <[EMAIL PROTECTED]> writes:
|
| [...]
|
| Walter> Is there something further I must do to have configure look
| Walter> in the correct place, as defined by the install-script?
|
| It should be enough to call AC_CONFIG_AUX_DIR *before* AM_INIT_AUTOMAKE.
|
| That's a classic gotcha. We ought to do something about this.
|
| [...]
