From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/2] Add 'make checks' and clang-checks to build system
Date: Fri, 4 Jun 2021 08:06:11 +0200 [thread overview]
Message-ID: <YLnC05icNAshbXtr@pevik> (raw)
In-Reply-To: <20210603154825.30165-2-rpalethorpe@suse.com>
Hi Richie,
> Allows the user to run 'make check' to check all source files or
> 'make check-<target>' to check one source file corresponding to a
> target.
> Adds makefile pieces for tools/clang-checks/main which will be a
> libclang based tool. By default this is ran by 'make check'.
Compilation does not work from tools directory:
$ cd tools/ && make
../include/mk/testcases.mk:25: ../include/mk/clang-checks.mk: No such file or directory
make: *** No rule to make target '../include/mk/clang-checks.mk'. Stop.
(works from tools/clang-checks/)
But even with compiled tools/clang-checks/main I'm not able to find how this is
supposed to be run, none of these work for me, what am I missing?
$ make autotools && ./configure
$ make check
make: *** No rule to make target 'check'. Stop.
$ make check-clang
make: *** No rule to make target 'check-clang'. Stop.
$ cd lib; make check
../include/mk/lib.mk:29: ../include/mk/clang-checks.mk: No such file or directory
make: *** No rule to make target '../include/mk/clang-checks.mk'. Stop.
$ cd ../testcases/kernel/syscalls/fchown/
make check
../../../../include/mk/testcases.mk:25: ../../../../include/mk/clang-checks.mk: No such file or directory
make: *** No rule to make target '../../../../include/mk/clang-checks.mk'. Stop.
$ tools/clang-checks/main
Failed to load translation unit: 4
=> maybe print some help info when running without parameters?
Kind regards,
Petr
> In theory allows other tools to be specified with
> 'make CHECK=tool CHECK_FLAGS=<args> check...'. e.g. 'make CHECK=sparse
> CHECK_FLAGS= check-tst_cgroup'
next prev parent reply other threads:[~2021-06-04 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:48 [LTP] [RFC PATCH 0/2] Libclang based analyzer Richard Palethorpe
2021-06-03 15:48 ` [LTP] [RFC PATCH 1/2] Add 'make checks' and clang-checks to build system Richard Palethorpe
2021-06-04 6:06 ` Petr Vorel [this message]
2021-06-04 6:12 ` Petr Vorel
2021-06-04 8:42 ` Richard Palethorpe
2021-06-04 8:55 ` Petr Vorel
2021-06-03 15:48 ` [LTP] [RFC PATCH 2/2] Start libclang based analyzer and TEST() check Richard Palethorpe
2021-06-04 6:20 ` [LTP] [RFC PATCH 0/2] Libclang based analyzer Petr Vorel
2021-06-04 9:03 ` Richard Palethorpe
2021-06-04 9:15 ` Petr Vorel
2021-06-04 11:34 ` Cyril Hrubis
2021-06-04 12:51 ` Petr Vorel
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=YLnC05icNAshbXtr@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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