lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Aug 2022 23:26:41 -0300 From: Tales Aparecida <tales.aparecida@...il.com> To: Sadiya Kazi <sadiyakazi@...gle.com> Cc: linux-kernel@...r.kernel.org, kunit-dev@...glegroups.com, linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org, davidgow@...gle.com, corbet@....net, brendan.higgins@...ux.dev, Trevor Woerner <twoerner@...il.com>, siqueirajordao@...eup.net, mwen@...lia.com, andrealmeid@...eup.net, mairacanal@...eup.net, Isabella Basso <isabbasso@...eup.net>, magalilemes00@...il.com, tales.aparecida@...il.com Subject: [PATCH v2 3/8] Documentation: KUnit: add note about mrproper in start.rst The "Getting Started" guide should be beginner-friendly, therefore add a note about the requirement of a clean source tree when running kunit_tool for the first time, and its related error. Signed-off-by: Tales Aparecida <tales.aparecida@...il.com> --- Notes: Edit note following suggestions (Sadiya Kazi) --- Documentation/dev-tools/kunit/start.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/Documentation/dev-tools/kunit/start.rst b/Documentation/dev-tools/kunit/start.rst index 2e31350a85e1..9beec7d6ac4b 100644 --- a/Documentation/dev-tools/kunit/start.rst +++ b/Documentation/dev-tools/kunit/start.rst @@ -19,6 +19,22 @@ can run kunit_tool: ./tools/testing/kunit/kunit.py run +.. note :: + You may see the following error: + "The source tree is not clean, please run 'make ARCH=um mrproper'" + + This happens because internally kunit.py specifies ``.kunit`` + (default option) as the build directory in the command ``make O=output/dir`` + through the argument ``--build_dir``. Hence, before starting an + out-of-tree build, the source tree must be clean. + + There is also the same caveat mentioned in the "Build directory for + the kernel" section of the :doc:`admin-guide </admin-guide/README>`, + that is, its use, it must be used for all invocations of ``make``. + The good news is that it can indeed be solved by running + ``make ARCH=um mrproper``, just be aware that this will delete the + current configuration and all generated files. + If everything worked correctly, you should see the following: .. code-block:: -- 2.37.2
Powered by blists - more mailing lists