%% Akim Demaille <[EMAIL PROTECTED]> writes:
ad> | 1) I had a line like this in my configure.in:
ad> | test -f somefile.in && AC_OUTPUT(somefile)
ad> Err, I suppose you mean AC_CONFIG_FILES. Two AC_OUTPUT is not
ad> supported by Autoconf.
Yes, precisely.
Anyway, I changed this t
>>> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes:
Thomas> On 22 Apr 2002, Akim Demaille wrote:
[...]
>> Two AC_OUTPUT is not supported by Autoconf.
Thomas> You ought to learn to phrase your sentences using
Thomas> accurate terminology. It's implemented, but in the
Thomas> inter
On 22 Apr 2002, Akim Demaille wrote:
>
> | 1) I had a line like this in my configure.in:
> | test -f somefile.in && AC_OUTPUT(somefile)
>
> Err, I suppose you mean AC_CONFIG_FILES. Two AC_OUTPUT is not
> supported by Autoconf.
You ought to learn to phrase your sentences using accurate ter
| 1) I had a line like this in my configure.in:
| test -f somefile.in && AC_OUTPUT(somefile)
Err, I suppose you mean AC_CONFIG_FILES. Two AC_OUTPUT is not
supported by Autoconf.
> "Paul" == Paul Smith writes:
Paul> 1) I had a line like this in my configure.in:
Paul> test -f somefile.in && AC_OUTPUT(somefile)
Paul>This works fine with configure, but automake really doesn't like it:
This may never work. Automake likes the outputs to be static.
With the swi
1) I had a line like this in my configure.in:
test -f somefile.in && AC_OUTPUT(somefile)
This works fine with configure, but automake really doesn't like it:
configure.in:337: required file `./test.in' not found
configure.in:337: required file `./-f.in' not found
conf
