>>>>> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> Hello, Akim!
Hi there!
> Why can't I use AC_CHECK_FILE when cross-compiling? If I need
> to look for a file that is used during the build then that has
> nothing to do with what the compiler does.
Pavel> I agree, this limitation seems ridiculous. But it's documented:
Pavel> "Check whether file FILE exists on the native system."
Well, if people agree this is reasonable, then I certainly won't fight
against this. The point was that Ken (IIRC he is the one who wrote
this macro) was using it for checking for the existence of
/dev/... and things like /etc/passwd...
These files, of course, are related to the host, certainly not the
build machine. That's why he decided to die when cross compiling.
I'm not in favor of removing this ``limitation'' because this macro
addresses well its point. If you want to check for the presence of a
DTD etc., then sorry, but it seems to me that it's a runtime issue.
If you really need to check for the existence of a file for the
*build* process, then AC_CHECK_FILE is just overkill: enjoy test -f!
And yes, AC_CHECK_FUNC checks for the presence of files, but *build*
files, not host files, so it is right.
I'm not *against* releasing the limitations, but it makes perfect
sense to me. I'm not convinced yet it's wrong. You have to convince
me you need AC_CHECK_FILE and not just test -f.
