From: Kevin Hilman Subject: Re: [RFD] How to support KBUILD_OUTPUT for kselftest? Date: Tue, 26 Jan 2016 11:47:40 -0800 Message-ID: <7hk2mwnmw3.fsf@baylibre.com> References: <56849D4B.6010008@linaro.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <56849D4B.6010008-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> (Bamvor Jian Zhang's message of "Thu, 31 Dec 2015 11:13:15 +0800") Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Bamvor Jian Zhang Cc: lkml , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Michael Ellerman , Mark Brown , Shuah Khan , Tyler Baker , dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org List-Id: linux-api@vger.kernel.org Bamvor Jian Zhang writes: > I am trying to improve cross compiling support for kselftest recently. Right > now I am stuck when I want to enable KBUILD_OUTPUT(O=xxx). It exist in wiki of > kselftest[1]. Hope it is not a duplicated work. Just want to echo the need for this feature because trying to build kselftests for a kernel built with KBUILD_OUTPUT is broken due to hard-coded assumptions about paths to headers, etc. I haven't dug any deeper into how to fix it though... Kevin