From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/1] configure.ac: Print lib & docparse summary
Date: Thu, 4 Nov 2021 14:14:56 +0100 [thread overview]
Message-ID: <YYPc0E/IUPBu1z2k@yuki> (raw)
In-Reply-To: <20211103160815.20282-1-pvorel@suse.cz>
Hi!
> Due many checks of structs, members etc are library presence and
> docparser config results quite hidden. Print them in the end.
Another option would be adding 'make info' target to the top level
Makefile that would print these based on config.mk, not sure if that
would be much better than this though.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-04 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 16:08 [LTP] [RFC PATCH 1/1] configure.ac: Print lib & docparse summary Petr Vorel
2021-11-04 13:14 ` Cyril Hrubis [this message]
2021-11-04 19:45 ` 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=YYPc0E/IUPBu1z2k@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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