From: Masahiro Yamada <masahiroy@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] kconfig: Qt5: tell the user which packages are required
Date: Sun, 24 Jul 2022 19:05:22 +0900 [thread overview]
Message-ID: <CAK7LNAR5uc5Ypw2MaukjbQbf9gXh0QpnhUpps7kNAeEbkF12og@mail.gmail.com> (raw)
In-Reply-To: <20220720173749.7487-1-rdunlap@infradead.org>
On Thu, Jul 21, 2022 at 2:38 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Along with saying "Please install Qt5 ...", tell exactly which
> parts of Qt5 are needed. This is useful when parts of Qt5 are
> installed but some of the required pieces are missing, and it
> eliminates the need for the user to find the shell script and
> the line in it that provide that information.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: linux-kbuild@vger.kernel.org
Applied to linux-kbuild.
Thanks.
> ---
> scripts/kconfig/qconf-cfg.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/scripts/kconfig/qconf-cfg.sh
> +++ b/scripts/kconfig/qconf-cfg.sh
> @@ -20,5 +20,6 @@ fi
> echo >&2 "*"
> echo >&2 "* Could not find Qt5 via ${HOSTPKG_CONFIG}."
> echo >&2 "* Please install Qt5 and make sure it's in PKG_CONFIG_PATH"
> +echo >&2 "* You need $PKG"
> echo >&2 "*"
> exit 1
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2022-07-24 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 17:37 [PATCH] kconfig: Qt5: tell the user which packages are required Randy Dunlap
2022-07-24 10:05 ` Masahiro Yamada [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=CAK7LNAR5uc5Ypw2MaukjbQbf9gXh0QpnhUpps7kNAeEbkF12og@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).