On 2014-07-14 02:33, Stephen Rothwell wrote: > Hi Sam, > > On Mon, 14 Jul 2014 10:29:36 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> >> On Sun, 13 Jul 2014 20:36:37 +0200 Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: >>> >>> NOTE: This will likely break the build if the toolchain used do >>> not include a libc. Let's see how much noise this creates. >> >> Then I will drop them from linux-next. Until someone supplies lots of >> cross compilers with libc support, the samples can not (must not) be >> built by default. > > Just to be clear: for my current build infrastructure, this means > powerpc and x86_64 hosted cross compilers. So we basically can have zero, one or both of A) target toolchain with libc support B) host toolchain with recent enough kernel headers Just can idea - in case we have B, but not A, would it make sense to build $(uapiprogs-y) with the host compiler, but without the -Iusr/include flag? The question is whether to add a kconfig knob for this, or some automatic detection for libc support of the target toolchain. I'll come up with a patch later. Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
