From: "Usama" <usama.anjum@collabora.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: usama.anjum@collabora.com, Shuah Khan <shuah@kernel.org>,
KERNEL SELFTEST FRAMEWORK <linux-kselftest@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"kernelci@groups.io" <kernelci@groups.io>
Subject: [Bug Report] - kselftest build fails if output directory is first level sub-directory
Date: Sat, 21 May 2022 11:44:32 +0500 [thread overview]
Message-ID: <c25d7ea7-4f72-4a2b-d8c3-d317e64fcbbb@collabora.com> (raw)
Hello,
kselftest can be built using the kernel's top most Makefile without
using kselftest's Makefile directly. But there is bug in the top most
Makefile. The build fails if the specified output directory is first
level sub-directory. Here is a example to reproduce this bug:
make kselftest-all O=build
"The Make is working in a wrong directory, that is why the relative path
does not work." Masahiro Yamada. Feel free to fix it if someone pin the bug.
It should be noted that the build works in some other combinations:
make kselftest-all (works)
make kselftest-all O=/tmp (works)
make kselftest-all O=build/build2 (works)
My unsuccessful attempt to fix this bug can be found here:
https://lore.kernel.org/lkml/20220223191016.1658728-1-usama.anjum@collabora.com/
Thanks,
Muhammad Usama Anjum
next reply other threads:[~2022-05-21 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 6:44 Usama [this message]
2022-05-22 17:15 ` [Bug Report] - kselftest build fails if output directory is first level sub-directory Masahiro Yamada
2022-05-23 9:40 ` Usama
2022-06-07 12:59 ` Usama
2022-06-07 21:39 ` Shuah Khan
2022-06-27 7:06 ` Usama
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=c25d7ea7-4f72-4a2b-d8c3-d317e64fcbbb@collabora.com \
--to=usama.anjum@collabora.com \
--cc=kernelci@groups.io \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=shuah@kernel.org \
/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