[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug#999510: libidn2 FTBFS for musl-linux-any: broken gettext check
From: |
Simon Josefsson |
Subject: |
Bug#999510: libidn2 FTBFS for musl-linux-any: broken gettext check |
Date: |
Wed, 24 Nov 2021 14:07:32 +0100 |
User-agent: |
Evolution 3.38.3-1 |
ons 2021-11-24 klockan 06:14 +0100 skrev Helmut Grohne:
> Hi Simon,
>
> On Tue, Nov 23, 2021 at 08:46:15PM +0100, Simon Josefsson wrote:
> > Hi. Thanks for the report. I don't understand, what error message
> > do
> > you get? As far as I can tell, that idiom is used in many GNU
> > packages,
> > and if we really should change, I think the change should be done
> > in
> > many packages. Is there anything unique to libidn2 here?
>
> You don't get any error message. The check simply considers that no
> libc
> other than glibc has a suitable gettext. The check is broken. That's
> why
> the check has been fixed upstream (in an incremented version). Yes,
> you're correct that many GNU packages need to bump up the version of
> the
> check. It's totally non-unique to libidn2. Other packages include
> bison
> and popt.
Thanks -- and including coreutils, I guess? Or are there other
workarounds or solutions to your problem than this fix?
I brought this up on the gnulib list:
https://lists.gnu.org/archive/html/bug-gnulib/2021-11/msg00029.html
If gnulib has a syntax-check rule for this problem, it will get fixed
in many more upstream projects indirectly. I'm a bit concerned that
there may be disagreement that your suggestion actually is the best
recommended general solution to the problem, but we'll see what the
response is.
/Simon
signature.asc
Description: This is a digitally signed message part