From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/usbutils: select libiconv if needed
Date: Tue, 4 Feb 2025 16:10:48 +0100 [thread overview]
Message-ID: <20250204161048.5ab4e27e@windsurf> (raw)
In-Reply-To: <b2769ce8-7d49-49df-a4da-3c69ef3886e3@armadeus.com>
On Tue, 4 Feb 2025 16:01:13 +0100
Sébastien Szymanski <sebastien.szymanski@armadeus.com> wrote:
> There is one failed build for the same reason for usbutils-015 [0]. On
> 2024.02, we have usbutils-017 so it can be backported there I guess.
>
> [0]
> http://autobuild.buildroot.net/results/a8e/a8e1961d91006fb6d99c0aaf3488a98af73e9143//
A better commit message is then:
"Since upstream commit 7c7fed30f7553b551fce3151fe315cf69e602065, which
first appeared in usbutils version 007, iconv is used when available.
Since then, the package has been failing to build when libiconv needs
to be provided by a library external to the C library. This commit
fixes that by ..."
This way, we clearly retrace the origin of the problem, instead of
"guessing".
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
prev parent reply other threads:[~2025-02-04 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 8:38 [Buildroot] [PATCH] package/usbutils: select libiconv if needed Sébastien Szymanski
2025-02-04 14:47 ` Thomas Petazzoni via buildroot
2025-02-04 15:01 ` Sébastien Szymanski
2025-02-04 15:10 ` Thomas Petazzoni [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=20250204161048.5ab4e27e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=sebastien.szymanski@armadeus.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