From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/e2fsprogs: Don't build docs for host
Date: Sat, 19 Apr 2025 23:30:26 +0200 [thread overview]
Message-ID: <20250419233026.2a04c201@windsurf> (raw)
In-Reply-To: <20250408-fix_e2fsprogs-v1-1-cc814171907a@rivosinc.com>
Hello Charlie,
On Tue, 08 Apr 2025 17:03:05 -0700
Charlie Jenkins <charlie@rivosinc.com> wrote:
> texinfo isn't provided for the host in buildroot, but e2fsprogs always
> attempts to build the documentation. The error that gets printed is as
> follows:
>
> /usr/bin/install: cannot stat 'libext2fs.info*': No such file or directory
> make[3]: [Makefile:363: install-doc-libs] Error 1 (ignored)
>
> This error is ignored but it is unnecessary.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> package/e2fsprogs/e2fsprogs.mk | 6 ++++++
> 1 file changed, 6 insertions(+)
But why is that an issue for the host variant of e2fsprogs and not the
target variant?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-19 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 0:03 [Buildroot] [PATCH] package/e2fsprogs: Don't build docs for host Charlie Jenkins
2025-04-19 21:30 ` Thomas Petazzoni via buildroot [this message]
2025-05-17 20:51 ` Peter Korsgaard
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=20250419233026.2a04c201@windsurf \
--to=buildroot@buildroot.org \
--cc=charlie@rivosinc.com \
--cc=thomas.petazzoni@bootlin.com \
/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