On Tue, Oct 21, 2014 at 06:04:51PM -0400, Peter Foley wrote: > The intention of these changes was to generate more compiliation > coverage for code in Documentation/ Sounds good. > The underlying issue is that this doesn't work for cross-compiling > because kbuild doesn't have cross-compile support for userspace code. Well, my testptp does cross compile just fine. All it needs is the glibc library bundled with the tool chain and the kernel headers. > I submitted a patch to disable building Documentation when > cross-compiling, as the consensus in the thread that resulted in that > patch (https://lkml.org/lkml/2014/10/8/510) was that implementing > targetprogs in kbuild was not currently worth it. So this patch did not make it in, right? Otherwise people wouldn't be disabling cross compilation ad hoc, like in the patch that started this thread. > I can try to take a crack at adding targetprogs support, but I'm > rather busy right now, so it may take a little while. No rush, please do. In the mean time, I would like to restore the testptp.mk that *does* cross compile, so that people may use the test program if they want. In fact I use this all the time, and so I am a bit annoyed that something working was deleted and replaced with something broken. Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
