Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]>
Subject: Re: [ISSUE] [CLOSED] Fix up intl and NLS on musl and glibc (for some few packages)
Date: Wed, 25 May 2022 04:14:46 +0200	[thread overview]
Message-ID: <20220525021446.YRR1Lf94eFzFc-XBo5WfCsmL6NfuilmoQLnyK3kDNDg@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

Closed issue by ericonr on void-packages repository

On a musl system, `xbps-query -p shlib-requires -Rs libintl` provides the list of packages that still depend on `libtintl` for some reason. Some of them hardcode usage of glibc'isms like `_nl_msg_cat_cntr`, but most don't, and we should be able to fix them to use musl's `gettext` impl. See #29240 for more details and an initial push.

musl doesn't protect programs from calling `gettex(NULL)`, which while undefined behavior per the Gettext manual, doesn't actually segfault there, so before pushing a package to not use `libintl`, please also verify that it does work cleanly with musl's gettext impl. We have a workaround patch for now (, but I would like to remove it at some point - at least GIMP, as one of the crashing applications, has been fixed.

Furthermore, lots of templates have `--disable-nls` or similar (grepping for `-nls` might work well?) for all archs or only for musl, which is not an ideal state of affairs; ideally, we'd always have internationalization support enabled and working. So hunting down such packages and also fixing them would be nice.

      parent reply	other threads:[~2022-05-25  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  3:05 [ISSUE] " ericonr
2022-05-11  2:12 ` github-actions
2022-05-25  2:14 ` github-actions [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220525021446.YRR1Lf94eFzFc-XBo5WfCsmL6NfuilmoQLnyK3kDNDg@z \ \

* 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).