From: "Du, Changbin" <changbin.du@intel.com>
To: Shuah Khan <shuah@kernel.org>
Cc: changbin.du@intel.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v2 1/4] selftests/Makefile: append a slash to env variable OUTPUT
Date: Wed, 28 Mar 2018 09:45:25 +0800 [thread overview]
Message-ID: <20180328014525.bl3iih4xvo74wedb@intel.com> (raw)
In-Reply-To: <b473e652-0953-63ec-c4bf-5c9306dc4f67@kernel.org>
On Tue, Mar 27, 2018 at 03:19:26PM -0600, Shuah Khan wrote:
> On 03/26/2018 09:11 PM, changbin.du@intel.com wrote:
> > From: Changbin Du <changbin.du@intel.com>
> >
> > The tools/build/Makefile.build use 'OUTPUT' variable as below example:
> > objprefix := $(subst ./,,$(OUTPUT)$(dir)/)
> >
> > So it requires the 'OUTPUT' already has a slash at the end.
> >
> > This patch can kill below odd paths:
> > make[3]: Entering directory '/home/changbin/work/linux/tools/gpio'
> > CC /home/changbin/work/linux/tools/testing/selftests/gpiolsgpio.o
> > CC /home/changbin/work/linux/tools/testing/selftests/gpiogpio-utils.o
> > LD /home/changbin/work/linux/tools/testing/selftests/gpiolsgpio-in.o
> >
> > A correct path should be:
> > /home/changbin/work/linux/tools/testing/selftests/gpio/lsgpio.o
> >
> > Signed-off-by: Changbin Du <changbin.du@intel.com>
>
> Are you seeing this when you run "make kselftest" - if gpio is the
> only test compile that fails, it should be fixed in gpio/Makefile,
> not is the common Makefile.
>
I only saw error in gpio, but I also saw some kselftest Makefiles having string concatenation
as '$(OUTPUT)$(dir)'. So the rule is not aligned all over. They just didn't produce any errors
so far.
By the way, is there a basic test for kselftest infrastructure? It seems it was always
reporting error when building it :(
> thanks,
> -- Shuah
--
Thanks,
Changbin Du
next prev parent reply other threads:[~2018-03-28 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 3:11 [PATCH v2 0/4] selftests: fix compiling issues changbin.du
2018-03-27 3:11 ` [PATCH v2 1/4] selftests/Makefile: append a slash to env variable OUTPUT changbin.du
2018-03-27 21:19 ` Shuah Khan
2018-03-28 1:45 ` Du, Changbin [this message]
2018-03-27 3:11 ` [PATCH v2 2/4] selftests/gpio: fix paths in Makefile changbin.du
2018-03-27 3:11 ` [PATCH v2 3/4] kselftest: install sanitized kernel headers before compiling changbin.du
2018-03-27 21:25 ` Shuah Khan
2018-03-27 3:11 ` [PATCH v2 4/4] selftests/bpf: fix compiling errors changbin.du
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180328014525.bl3iih4xvo74wedb@intel.com \
--to=changbin.du@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®