| * Akim
| | [...] Your patch, as is, does not solve [...]
|
| I know, I know. I don't claim the patch to be perfect, I'm just saying
| that it is _better_ than the code it replaces. :^}
|
| | [...] since AC_PROG_CC launches AC_EXEEXT which uses AC_LINK_IFELSE
| | which requires AC_PROG_CC, autoconf should and will fail. This is
| | the circular dependency I'm referring to.
| |
| | AC_LINK_IFELSE must keep its AC_REQUIRE on AC_PROG_CC, hence you
| | must not use AC_LINK_IFELSE. That's why I first suggested using
| | AC_TRY_EVAL: to avoid the AC_REQUIRE.
|
| Yes, I was aware of that problem -- I just can't think of a good way
| to solve it at the moment.
Then let me restate my question: why don't you use AC_TRY_EVAL just
like in AC_EXEXT: this is a good first step I think.
| | You may call AC_CANONICAL_TARGET (while AC_CANONICAL_HOST is more
| | logical), but you must depend on the *_host variables, *not* the
| | target vars. See the doc for more details.
|
| I think the attached patch will at least improve the situation a
| little bit. I couldn't find anything from config.guess matching the
| EMX/OS2 stuff, though.
This patch is OK with me. But it is a first step: as is it means that
any configure.in using a compiler will require AC_CANONICAL_HOST,
which is not good. But the plan is to remove the call to AC_CYGWIN
etc. from AC_PROG_CC, so it is OK.
