From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] README: list the development packages required to build the library
Date: Thu, 4 Jul 2024 22:50:51 +0800 [thread overview]
Message-ID: <20240704145051.GA95228@rigel> (raw)
In-Reply-To: <20240704142451.28400-1-brgl@bgdev.pl>
On Thu, Jul 04, 2024 at 04:24:51PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> The error messages emitted by configure when either libtool, pkg-config
> or autoconf-archive packages are missing on the host are not very clear
> and seem to cause confusion among users building the project from
> sources. List the required packages in the README.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> README | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/README b/README
> index a6f24d1..a20e801 100644
> --- a/README
> +++ b/README
> @@ -34,6 +34,11 @@ BUILDING
> This is a pretty standard autotools project. The core C library does not have
> any external dependencies other than the standard C library with GNU extensions.
>
> +The build system requires autotools, autoconf-archive, libtool and pkg-config
> +to be installed on the host system for the basic build. Development files for
> +additional libraries may be required depending on selected options. The
> +configure script will typically prompt the user for them clearly when missing.
> +
typically? Shouldn't that always be the case?
"prompt" makes it seem interactive.
I would reword as "The configure script will report any missing additional
required dependencies."
Cheers,
Kent.
next prev parent reply other threads:[~2024-07-04 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 14:24 [libgpiod][PATCH] README: list the development packages required to build the library Bartosz Golaszewski
2024-07-04 14:50 ` Kent Gibson [this message]
2024-07-04 14:57 ` Bartosz Golaszewski
2024-07-04 15:10 ` Kent Gibson
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=20240704145051.GA95228@rigel \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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).