Hello, Lars!
> : Are you suggesting that "autoconf" issues a warning as well?
>
> Yes, if there's no case where generating a configure-script under such a
> circumstance is useful...
It has a low priority for me. I'll not object if anybody else does it.
> Anyways, I just found the problem. I originally had a script in top_srcdir
> that was used for ac_unique_file, but after it had grown a while I moved
> to its own project. With my setup, I therefore got a _directory_ with that
> name in the parent dir for the new project, which must have been the cause
> for silincing configure with that respect.
>
> Maybe the ac_unique_file test should ensure that ac_unique_file really is a
> file?
Certainly no. I've seen many cases when a directory (even ".") is used.
Regards,
Pavel Roskin
