Set config to compy to new coding standard
make configure: Includes wrong subdirectory

Seems to work either way. Corrected anyway as it's obviously wrong.

Remaining issue:
===============
* 'make configure' still runs autoconf twice.
* "warning: AC_REQUIRE: `AC_PROG_CC' was expanded before it was required"
Tool-chain include detection and deployment

* CHAINPATH in make-files (GNU) is removed. I.e. CHAINPATH is not given on
  command-line even when compiling singe source files manually anymore.
* TK_MULTI_ARCH_TARGET affecting sys/ include paths retired
  (BUILDCHAIN_MUARCH). This patch solves two problems in one.
* In stead: Two config.h macros CHAINPATH_INCLUDE and CHAINPATH_SYS_INCLUDE
* X-tools build with header-files at non-standard positions should be
  handled.

Change makes it much easier for application projects to set up build. Among
others, one can no longer can include the wrong file by mistake, thereby
(on hosted-mode builds) accidentally use the wrong API.

It appears (for hosted-mode builds) where header-files reside can vary
greatly even in cases which are not MULTI_ARCH_TARGET (Chrubuntu using ARM
Exynos).

There may furthermore exist several instances of standard library
header-files (at least named the same).

By asking the build-chain gcc (see aclocal.m4 in this path) any uncertainties
are removed. Gcc for the target tool-chain will respond where the
header-file directories are by inspecting the built-in search path:s.
Inspecting them in reversed order and take the first one find of a well
known files in "include" and "include/sys" respectively, one gets the build
in path (i.e. mechanism will not get confused by additional -I flags).

Old detector mechanisms left in place (just "actuators" are changed). This
should keep existing user-configs from breaking.
armv7l: Chrbuntu on Samsung Exynos

Hosted-mode added.

Bootstraps, configures
Segfaults on run at thread_creation.