Akim Demaille wrote:
>
> | AFAIS, one cause for this to happen at all, is presence of /lib/cpp
> | in this fragment from AC_PROG_CPP:
> |
> | # Double quotes because CPP needs to be expanded
> | for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp"
> | do
> | _AC_PROG_PREPROC_WORKS_IFELSE([break])
> | done
> |
> | If cross-compiling this causes AC_PROG_CPP to pick up the wrong cpp
> | (/lib/cpp) if $CC -E fails for whatever reason.
>
> Well, then we should dig to understand why it fails, but we can't just
> use -E.
Hmm, I think we might be talking past each other:
All I am trying to say is:
This check checks for a tool which is not applicable/illegal to use
for cross compilation (/lib/cpp is a native build-host tool).
As a side-effect of this it will silently pick up a wrong tool
instead of complaining/aborting if $CC -E fails.
Ralf
