If the configure script emits cross-compilation warnings like this:

cc1: warning: include location "/usr/local/include" is unsafe for cross-compilation [-Wpoison-system-directories]

Then the do_qa_configure() sanity tests will catch that but output it badly:

"This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.  Rerun configure task after fixing this. The path was '%s'"

Where %s is the root of the work directory.

The message should either not tell the user a misleading path (the work directory path), or tell the user the actual path that upset gcc.  (probably the former)