From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: bernd.kuhls@t-online.de, buildroot@buildroot.org,
Thomas Devoogdt <thomas.devoogdt@barco.com>
Subject: Re: [Buildroot] [PATCH v1] package/icu: disable icu config
Date: Thu, 1 Jan 2026 17:53:46 +0100 [thread overview]
Message-ID: <20260101175346.47e2d139@windsurf> (raw)
In-Reply-To: <20251025143557.79322-1-thomas@devoogdt.com>
Hello Thomas,
On Sat, 25 Oct 2025 16:35:57 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> From: Thomas Devoogdt <thomas.devoogdt@barco.com>
>
> Seen while using BR2_PER_PACKAGE_DIRECTORIES, not sure on how to reproduce.
>
> Fixes:
>
> /usr/bin/install: cannot stat 'config/icu-config.1': No such file or directory
> 2025-10-25T00:09:10 make[2]: *** [Makefile:359: install-manx] Error 1
> 2025-10-25T00:09:10 make[2]: Leaving directory '/home/thomas/buildroot/build/output/build/host-icu-73-2/source'
> 2025-10-25T00:09:10 make[1]: *** [Makefile:153: install-recursive] Error 2
> 2025-10-25T00:09:10 make[1]: *** Waiting for unfinished jobs....
> 2025-10-25T00:09:10 make[1]: Leaving directory '/home/thomas/buildroot/build/output/build/host-icu-73-2/source'
> 2025-10-25T00:09:10 make: *** [package/pkg-generic.mk:283: /home/thomas/buildroot/build/output/build/host-icu-73-2/.stamp_host_installed] Error 2
> 2025-10-25T00:09:10 make: *** Waiting for unfinished jobs....
Thanks for the patch, but the explanation is a bit weak I'm afraid. Is
this a parallel build issue within the icu build system?
The thing is that even if icu-config might be deprecated by the ICU
developers, how many packages using ICU still use icu-config?
Such a change would need at least a bit of analysis of how many
Buildroot packages rely on icu, and a test build of those packages
after removing icu-config. We don't need a 100% coverage testing on
this, but at least some sanity checking with a majority of packages
using icu, to see how bad the breakage might be (or not).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-01 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:34 [Buildroot] [PATCH 1/1] package/icu: disable icu-config for host package Bernd Kuhls
2023-05-16 19:03 ` Yann E. MORIN
[not found] ` <20230516190356.GP2582048__25958.2416781754$1684263867$gmane$org@scaer>
2023-05-16 19:08 ` Bernd Kuhls
2023-05-16 20:40 ` Yann E. MORIN
2025-10-25 14:35 ` [Buildroot] [PATCH v1] package/icu: disable icu config Thomas Devoogdt
2026-01-01 16:53 ` Thomas Petazzoni via buildroot [this message]
2026-01-03 11:07 ` [Buildroot] [PATCH v2] package/icu: disable icu-config Thomas Devoogdt
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=20260101175346.47e2d139@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=thomas.devoogdt@barco.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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