Re: What is meant by, "XXX does not appear in AM_CONDITIONAL"?

2005-01-08 Thread Bruce Korb
On Saturday 08 January 2005 01:53 pm, Alexandre Duret-Lutz wrote: > >>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes: > > Bruce> The problem is is that XXX *DOES* actually appear in an > AM_CONDITIONAL. > > But these macros are not evaluated because of your quoting, so > effectively XXX is

Re: What is meant by, "XXX does not appear in AM_CONDITIONAL"?

2005-01-08 Thread Alexandre Duret-Lutz
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes: Bruce> The problem is is that XXX *DOES* actually appear in an AM_CONDITIONAL. But these macros are not evaluated because of your quoting, so effectively XXX is not defined at all. [...] Bruce> [`some-shell-script-test` Bruce> if test $? -

Never mind: Re: What is meant by, "XXX does not appear

2005-01-08 Thread Bruce Korb
RTFM: The shell CONDITION (suitable for use in a shell `if' statement) is evaluated when `configure' is run. Note that you must arrange for _every_ `AM_CONDITIONAL' to be invoked every time `configure' is run - if `AM_CONDITIONAL' is run conditionally (e.g., in a shell `i

What is meant by, "XXX does not appear in AM_CONDITIONAL"?

2005-01-08 Thread Bruce Korb
The problem is is that XXX *DOES* actually appear in an AM_CONDITIONAL. Right in the "configure.ac" file, actually. So, obviously, it is having some problem actually finding the AM_CONDITIONAL not not being clear enough for me to fix the issue. Is it necessary to macroize the text and only use th