Hi!

It's not possible to use AC_PATH_PROGS_FEATURE_CHECK with a cache
variable that does not start with ac_cv_path_ which is bad since
one project might check for a certain capability of tool foo, while
some other project is interested in some completely orthogonal
capability of that same tool foo. As written, it is very likely that
both projects will use the cache variable ac_cv_path_FOO for
orthogonal purposes, which is bad by design.

Or have I misread something?

(Yes, I know that I can save ac_cv_path_FOO someplace else for
the duration of the AC_PATH_PROGS_FEATURE_CHECK macro, then extract
"my" result, then restore ac_cv_path_FOO, but that's just too ugly)

Cheers,
Peter

Reply via email to