From: shuah <shuah@kernel.org>
To: Deepa B <deepa01012015@gmail.com>, linux-kselftest@vger.kernel.org
Cc: shuah <shuah@kernel.org>
Subject: Re: kselftest build error: ../lib.mk: No such file or directory
Date: Wed, 8 Apr 2020 09:06:51 -0600 [thread overview]
Message-ID: <38bb916a-b8b4-143e-48aa-594bc8ff546c@kernel.org> (raw)
In-Reply-To: <CANmdEh3Ukq6+WbdN49B0uPZqC0Cm=jve=cL9vFv1YYaXHqL63Q@mail.gmail.com>
On 4/7/20 11:51 PM, Deepa B wrote:
> Hello,
> I'm running kselftest on Ubuntu 16.04lts.
> Details:
> deepa@deepa-Inspiron-3576:/usr/src/linux-headers-4.15.0-88/Documentation$
> uname -a
> Linux deepa-Inspiron-3576 4.15.0-91-generic #92~16.04.1-Ubuntu SMP Fri
> Feb 28 14:57:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>
> Command:
> deepa@deepa-Inspiron-3576:/usr/src/linux-headers-4.15.0-91-generic$
> make -C tools/testing/selftests
>
> Error:
> make: Entering directory
> '/usr/src/linux-headers-4.15.0-91/tools/testing/selftests'
> make[1]: Entering directory
> '/usr/src/linux-headers-4.15.0-91/tools/testing/selftests/android'
> Makefile:7: ../lib.mk: No such file or directory
> make[1]: *** No rule to make target '../lib.mk'. Stop.
> make[1]: Leaving directory
Looks like you are trying to build in /usr/src/linux-headers-4.15.0-88
This doesn't contain any source files.
Go down into directorties below selftest or
/usr/src/linux-headers-4.15.0-88/kernel you will see that there are
no .[ch] files in these directories.
You have to install Ubuntu 16.04lts source package for kernel or
checkout kernel git repos to build kernel and selftests for that
kernel from sources.
thanks,
-- Shuah
prev parent reply other threads:[~2020-04-08 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 5:51 kselftest build error: ../lib.mk: No such file or directory Deepa B
2020-04-08 15:06 ` shuah [this message]
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=38bb916a-b8b4-143e-48aa-594bc8ff546c@kernel.org \
--to=shuah@kernel.org \
--cc=deepa01012015@gmail.com \
--cc=linux-kselftest@vger.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