From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/1] configure.ac: Print summary
Date: Thu, 2 Dec 2021 21:30:06 +0100 [thread overview]
Message-ID: <20211202203006.32259-1-pvorel@suse.cz> (raw)
Due many checks of structs, members etc are chosen testsuites,
presence of used libraries and docparser config results quite hidden.
Print them as summary in the end.
Disadvantage of this is need to keep sync m4 macros with configure.ac
also quite easily results can be misinterpreted.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
configure.ac | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/configure.ac b/configure.ac
index 4751b14d2..063a8a9d1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -381,3 +381,26 @@ test "x$with_tirpc" = xyes && LTP_CHECK_TIRPC
LTP_DETECT_HOST_CPU
AC_OUTPUT
+
+cat << EOF
+
+TESTSUITES
+open posix testsuite: ${with_open_posix_testsuite:-no}
+realtime testsuite: ${with_realtime_testsuite:-no}
+
+LIBRARIES
+keyutils: ${have_keyutils:-no}
+libacl: ${have_libacl:-no}
+libaio: ${have_libaio:-no} (aio: ${have_aio:-no})
+libcap: $cap_libs (newer: ${has_newer_libcap:-no})
+libcrypto: $have_libcrypto (sha: ${have_sha:-no})
+libmnl: ${have_libmnl:-no}
+libnuma: ${have_libnuma:-no} (headers: ${have_numa_headers:-no}, v2 headers: ${have_numa_headers_v2:-no})
+libtirpc: ${have_libtirpc:-no}
+glibc SUN-RPC: ${have_rpc_glibc:-no}
+
+METADATA
+metadata generator: $with_metadata_generator
+HTML metadata: $with_metadata_html
+PDF metadata: $with_metadata_pdf
+EOF
--
2.34.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2021-12-02 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 20:30 Petr Vorel [this message]
2021-12-03 11:09 ` [LTP] [PATCH v2 1/1] configure.ac: Print summary Jan Stancek
2021-12-06 10:26 ` Petr Vorel
2021-12-07 13:01 ` Richard Palethorpe
2021-12-07 17:09 ` Petr Vorel
2021-12-07 19:42 ` Cyril Hrubis
2021-12-08 5:43 ` 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=20211202203006.32259-1-pvorel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.