vim-core can not be compiled with nls enabled and thus that flag should be masked in those profiles. The failure is: msgfmt: Cannot convert from "CP932" to "UTF-8". msgfmt relies on iconv(), and iconv() does not support this conversion. I think the rest of build log is unrelevant but can be attached if requested
Yes, please attach the build log and provide emerge --info.
Created attachment 864380 [details] build.log
Created attachment 864381 [details] emerge --info
I am running into same issue. Also clang/musl profile. I've attached build.log and emerge --info
This is likely gettext-0.22 combined with musl.
I suspect Bruno's comment to me is applicable here as well: <bhaible[m]> About https://bugs.gentoo.org/908863: The error message "msgfmt: present charset "ISO-8859-16" is not a portable encoding name" is clear. The PO file should be converted to another encoding, e.g. through msgconv. Too few platforms support this encoding, see https://www.haible.de/bruno/charsets/conversion-tables/ISO-8859-16.html (He was talking about another bug.) This should probably be reported upstream to vim as well.
same here at 17.0_musl_hardened-20230814-144751/
Maybe obvious, but USE=-nls is a temporary workaround.
Exherbo did https://gitlab.exherbo.org/exherbo/arbor/-/commit/7b5794e370ed95059ecde5f2131c7538f7ab6b42.
same error for musl-gcc
*** Bug 921318 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aea8deb234226dd8b318d720a7b2a6f963408791 commit aea8deb234226dd8b318d720a7b2a6f963408791 Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2024-01-11 19:27:19 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2024-01-11 19:28:06 +0000 profiles/features/musl: mask latest Vim Fails to compile Bug: https://bugs.gentoo.org/908961 Signed-off-by: Fabian Groffen <grobian@gentoo.org> profiles/features/musl/package.mask | 5 +++++ 1 file changed, 5 insertions(+)
It's probably better to just mask USE=nls for musl instead, given I don't think most musl users worry about it much.
What Exherbo is doing is much less affecting than masking entire USE=nls. Are there concerns for doing that in a elibc_musl block in the three ebuilds?
(In reply to Fabian Groffen from comment #14) > What Exherbo is doing is much less affecting than masking entire USE=nls. > Are there concerns for doing that in a elibc_musl block in the three ebuilds? fine with me, i think the proxied maint is away atm on holiday
tinderbox_musl has reproduced this issue with version 9.0.2167 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83d72770bcd85405144b4a6ad2b427abc11fe62c commit 83d72770bcd85405144b4a6ad2b427abc11fe62c Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2024-01-19 07:33:03 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2024-01-19 07:34:44 +0000 app-editors/{vim-core,vim,gvim}: disable CP932 for musl builds Closes: https://bugs.gentoo.org/908961 Signed-off-by: Fabian Groffen <grobian@gentoo.org> app-editors/gvim/gvim-9.0.2167.ebuild | 5 +++++ app-editors/gvim/gvim-9999.ebuild | 5 +++++ app-editors/vim-core/vim-core-9.0.2167.ebuild | 5 +++++ app-editors/vim-core/vim-core-9999.ebuild | 5 +++++ app-editors/vim/vim-9.0.2167.ebuild | 5 +++++ app-editors/vim/vim-9999.ebuild | 5 +++++ 6 files changed, 30 insertions(+)
