[..] fmtutil [INFO]: --- remaking dviluatex with luatex fmtutil: running `luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini' ... Unable to read environment locale: exit now. fmtutil [ERROR]: running `luahbtex -ini -jobname=luahbtex -progname=luahbtex luatex.ini </dev/null' return status: 1 fmtutil [ERROR]: cannot copy log luahbtex.log to: /var/tmp/portage/dev-texlive/texlive-basic-2021/work/texmf-var/web2c/luahbtex fmtutil [ERROR]: returning error due to option --strict fmtutil [ERROR]: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini </dev/null' return status: 1 fmtutil [ERROR]: cannot copy log luatex.log to: /var/tmp/portage/dev-texlive/texlive-basic-2021/work/texmf-var/web2c/luatex fmtutil [ERROR]: returning error due to option --strict fmtutil [ERROR]: running `luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini </dev/null' return status: 1 fmtutil [ERROR]: cannot copy log dviluatex.log to: /var/tmp/portage/dev-texlive/texlive-basic-2021/work/texmf-var/web2c/luatex fmtutil [ERROR]: returning error due to option --strict fmtutil [INFO]: successfully rebuilt formats: 5 fmtutil [INFO]: failed to build: 3 (luahbtex/luahbtex luatex/luatex luatex/dviluatex) fmtutil [INFO]: total formats: 8 fmtutil [INFO]: total formats: 8 fmtutil [INFO]: exiting with status 3 * ERROR: dev-texlive/texlive-basic-2021::gentoo failed (compile phase): * failed to build format texmf-dist/fmtutil/format.texlive-basic.cnf * * Call stack: * ebuild.sh, line 127: Called src_compile * environment, line 523: Called texlive-module_src_compile * environment, line 734: Called die * The specific snippet of code: * VARTEXFONTS="${T}/fonts" TEXMFHOME="${S}/texmf:${S}/texmf-dist:${S}/texmf-var" env -u TEXINPUTS $fmt_call --cnffile "${i}" --fmtdir "${S}/texmf-var/web2c" --all || die "failed to build format ${i}"; [..]
Created attachment 724291 [details] Build log
lua specific stuff fail if LANG is unset. what happens after `export LANG=C`?
(In reply to Mikle Kolyada from comment #2) > what happens after `export LANG=C`? That seems to work around it — cool! Could something like… export LANG="${LANG:-C}" …be added to the ebuild to make it more robust? It's the only package that I have seen cause trouble like that in quite a while in that LANG-less setup of mine.
I remember there were more ebuilds to fail if no LANG is defined, so might be better to define it straight in the eclass...
(In reply to Mikle Kolyada from comment #4) > I remember there were more ebuilds to fail if no LANG is defined, so might > be better to define it straight in the eclass... I mean texlive ebuilds :)
I just hit this. What's the recommended solution right now so that it can be installed?
(In reply to Nikos Chantziaras from comment #6) > I just hit this. What's the recommended solution right now so that it can be > installed? Hm. Never mind. I had to re-run: $ sudo localectl set-locale LANG=en_US.UTF-8 On my system. For some reason, LANG was set to "en_US.utf8", which apparently makes perl print warnings about not being able to set the locale. On top of that, I had to: $ rm ~/.config/plasma-localerc on my KDE system. It seems it was responsible for overriding my locale with "en_US.utf8". I have no idea which of those two things fixed it, but one of them did.
(In reply to Nikos Chantziaras from comment #7) > (In reply to Nikos Chantziaras from comment #6) > > I just hit this. What's the recommended solution right now so that it can be > > installed? > > Hm. Never mind. I had to re-run: > > $ sudo localectl set-locale LANG=en_US.UTF-8 > > On my system. For some reason, LANG was set to "en_US.utf8", which > apparently makes perl print warnings about not being able to set the locale. > > You probably didn't have that locale generated.
