On 12/09/2010 03:34 PM, Michal Marek wrote: > On 9.12.2010 16:24, Asbjoern Sloth Toennesen wrote: >> Usefull if building for sparc64 userland, because the >> sparc and sparc64 userlands use the same 64-bit kernel, >> making it impossible to always select the correct userland >> architecture for the resulting debian package. >> >> Might also be usefull, if you want a i386 userland with a amd64 kernel. >> >> Example usage: >> make KBUILD_DEBARCH=i386 deb-pkg >> >> LKML-reference: <alpine.DEB.2.02.1011051437500.13287@xxxxxxxxxxxxxxxx> >> Signed-off-by: Asbjoern Sloth Toennesen <asbjorn@xxxxxxxxxxx> >> Reviewed-by: WANG Cong <xiyou.wangcong@xxxxxxxxx> >> Acked-by: maximilian attems <max@xxxxxxx> >> --- >> Documentation/kbuild/kbuild.txt | 8 ++++++++ >> scripts/package/builddeb | 3 +++ >> 2 files changed, 11 insertions(+), 0 deletions(-) >> >> diff --git a/Documentation/kbuild/kbuild.txt b/Documentation/kbuild/kbuild.txt >> index 634c625..9cf3bf0 100644 >> --- a/Documentation/kbuild/kbuild.txt >> +++ b/Documentation/kbuild/kbuild.txt >> @@ -60,6 +60,14 @@ But some architectures such as x86 and sparc have aliases. >> x86: i386 for 32 bit, x86_64 for 64 bit >> sparc: sparc for 32 bit, sparc64 for 64 bit >> >> +KBUILD_DEBARCH >> +-------------------------------------------------- >> +For the deb-pkg target, allows overriding the normal heuristics deployed by >> +deb-deb. Normally deb-pkg attempts to guess the right architecture based on > ^^^^^^^ > > deb-pkg? Sure. Anything else before I make a v4? -- 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
