| View previous topic :: View next topic |
| Author |
Message |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
 Posted: Fri Jun 28, 2019 10:48 am Post subject: texlive-basic-2019-r1 fails: Can't locate mktexlsr.pl |
 |
|
This bug was recently closed as invalid, on the argument that this is a problem with perl, not texlive. Installation fails with the following:
| Code: | * Building format texmf-dist/fmtutil/format.texlive-basic.cnf
Can't locate mktexlsr.pl in @INC (@INC contains: //tlpkg //texmf-dist/scripts/texlive /etc/perl /usr/local/lib64/perl5/5.30.0/x86_64-linux /usr/local/lib64/perl5/5.30.0 /usr/lib64/perl5/vendor_perl/5.30.0/x86_64-linux /usr/lib64/perl5/vendor_perl/5.30.0 /usr/local/lib64/perl5 /usr/lib64/perl5/vendor_perl/5.12.4 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/5.30.0/x86_64-linux /usr/lib64/perl5/5.30.0) at /usr/bin/fmtutil line 23.
BEGIN failed--compilation aborted at /usr/bin/fmtutil line 25.
* ERROR: dev-texlive/texlive-basic-2019-r1::gentoo failed (compile phase):
* failed to build format texmf-dist/fmtutil/format.texlive-basic.cnf
*
* Call stack:
* ebuild.sh, line 124: Called src_compile
* environment, line 545: Called texlive-module_src_compile
* environment, line 741: 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}";
*
* If you need support, post the output of `emerge --info '=dev-texlive/texlive-basic-2019-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-texlive/texlive-basic-2019-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work'
* S: '/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work'
|
build.log is on the bugreport.
Can anybody explain to me what's wrong with my perl installation that this won't install?
Thanks for the help!
EE |
|
| Back to top |
|
 |
John R. Graham
Administrator
Joined: 08 Mar 2005
Posts: 10702
Location: Somewhere over Atlanta, Georgia
|
| Posted: Fri Jun 28, 2019 6:05 pm Post subject: |
|
|
When I induced the failure by removing "/usr/share/texmf-dist/scripts/texlive/mktexlsr.pl", I got a subtly different failure than you did: | Code: | Can't locate mktexlsr.pl in @INC (@INC contains: /usr/share/tlpkg /usr/share/texmf-dist/scripts/texlive /etc/perl /usr/local/lib64/perl5/5.28.2/x86_64-linux /usr/local/lib64/perl5/5.28.2 /usr/lib64/perl5/vendor_perl/5.28.2/x86_64-linux /usr/lib64/perl5/vendor_perl/5.28.2 /usr/local/lib64/perl5 /usr/lib64/perl5/vendor_perl/5.26.2 /usr/lib64/perl5/vendor_perl/5.24.3 /usr/lib64/perl5/vendor_perl/5.24.1 /usr/lib64/perl5/vendor_perl/5.22.3 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/5.28.2/x86_64-linux /usr/lib64/perl5/5.28.2) at /usr/bin/fmtutil line 23.
BEGIN failed--compilation aborted at /usr/bin/fmtutil line 25.
* ERROR: dev-texlive/texlive-basic-2019-r1::gentoo failed (compile phase):
* failed to build format texmf-dist/fmtutil/format.texlive-basic.cnf |
See the difference? It appears that the ebuild-added Perl include path members are messed up. Haven't tracked down further than that yet. But it seems likely that Perl is not at fault.
One wild guess. Is this a prefix install?
Builds correctly here, by the way.
- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Sat Jun 29, 2019 3:13 am Post subject: |
|
|
Hi John,
thanks for your reply. This is not a prefix install. 'locate mktexlsr.pl' reports that file at:
| Code: | # locate mktexlsr.pl
/home/[$TEXLOCAL]/tex-local/texlive/2017/texmf-dist/scripts/texlive/mktexlsr.pl
/usr/share/texmf-dist/scripts/texlive/mktexlsr.pl |
I have a local installation I installed manually in a subdirectory of my /home/, but the system one is where it appears it should be.
Any other suggestions?
Cheers,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Fri Aug 16, 2019 4:07 pm Post subject: |
|
|
UPDATE: I'm still having this issue. Any suggestions on why the installer can't find mktexlsr.pl?
Cheers,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Mon Aug 26, 2019 4:01 pm Post subject: |
|
|
UPDATE: I went and looked in /usr/bin/fmtutil to see why this was failing. The relevant block of code reads:
| Code: | my $TEXMFROOT;
BEGIN {
$^W = 1;
$TEXMFROOT = `kpsewhich -var-value=TEXMFROOT`;
if ($?) {
die "$0: kpsewhich -var-value=TEXMFROOT failed, aborting early.\n";
}
chomp($TEXMFROOT);
unshift(@INC, "$TEXMFROOT/tlpkg", "$TEXMFROOT/texmf-dist/scripts/texlive");
require "mktexlsr.pl";
TeX::Update->import();
}
|
'which kpsewhich' returns "/usr/bin/kpsewhich", so I'm not using a prefix for that. But when I do 'kesewhich -var-value=TEXMFROOT', from the console, it returns "/", which is definitely wrong.
So my TEXMFROOT prefix was never set properly, and I suspect this is why this install is failing. How do I fix this?
Cheers,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Mon Aug 26, 2019 5:01 pm Post subject: |
|
|
UPDATE: setting 'export TEXMFROOT=/usr/share/' before I start the emerge gets past that point, but now it fails on this:
| Code: | * Building format texmf-dist/fmtutil/format.texlive-basic.cnf
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil: texmf-dist/fmtutil/format.texlive-basic.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil: texmf-dist/fmtutil/format.texlive-basic.cnf
fmtutil [INFO]: writing formats under /var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work/texmf-var/web2c
fmtutil [INFO]: --- remaking pdftex with pdftex
fmtutil: running `pdftex -ini -jobname=pdftex -progname=pdftex -translate-file=cp227.tcx *pdfetex.ini' ...
warning: Could not open char translation file `cp227.tcx'.
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019 Gentoo Linux) (INITEX)
restricted \write18 enabled.
entering extended mode
(/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work/texmf-dist/tex/plain/c
onfig/pdfetex.ini
(/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work/texmf-dist/tex/generic
/tex-ini-files/pdftexconfig.tex)
(/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work/texmf-dist/tex/plain/e
tex/etex.src
(/var/tmp/portage/dev-texlive/texlive-basic-2019-r1/work/texmf-dist/tex/plain/b
ase/plain.tex Preloading the plain format: codes, registers, parameters,
fonts, more fonts, macros, math definitions, output routines, hyphenation
! I can't find file `hyphen'.
l.1222 \input hyphen
|
So it looks like it's still unable to find files. Any suggestions?
I have a texlive installation residing under /home; should I just tell everything to use that and uninstall all this stuff from the system?
Cheers,
EE |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Fri Nov 08, 2019 7:19 am Post subject: |
|
|
UPDATE: I was told that the problem I'm having is due to a misconfigured kpathsea. I don't know how to fix that. In the file /etc/texmf/texmf.d/05searchpaths.cnf, I have the following variables declared:
| Code: |
TEXMFROOT = $SELFAUTODIR/share
% The main tree of distributed packages and programs:
TEXMFDIST = $TEXMFROOT/texmf-dist
% We used to have a separate /texmf tree with some core programs and files.
% Keep the variable name.
TEXMFMAIN = $TEXMFDIST
% The Gentoo site tree
TEXMFSITE = $TEXMFROOT/texmf-site
% Local additions to the distribution trees.
TEXMFLOCAL = $TEXMFROOT/../local/share/texmf
|
All of those look standard.
Where else can I look to see why my local kpathsea config is messed up?
Thanks |
|
| Back to top |
|
|
*zensiert*
n00b
Joined: 10 Oct 2004
Posts: 55
Location: Germany
|
| Posted: Sat Nov 16, 2019 10:55 am Post subject: |
|
|
I had the same problem and was able to fix it as follows:
Then uninstall all packages returned by the previous command
Finally, delete /etc/texmf (you might want to back it up before):
After that I was able to install texlive-basic-2019-r1 without a problem. |
|
| Back to top |
|
|
jeffk
l33t
Joined: 13 Sep 2003
Posts: 671
|
| Posted: Mon Apr 27, 2020 5:47 pm Post subject: |
|
|
| ExecutorElassus wrote: | | UPDATE: I was told that the problem I'm having is due to a misconfigured kpathsea. I don't know how to fix that. Where else can I look to see why my local kpathsea config is messed up? |
I'm having the exact same symptoms, first encountered during the package upgrade to texlive-2020 et al. I've followed the suggestion of the next reply to unmerge, clear /etc/texmf, remerge (using texlive-2019 which was formerly working), and now they are having very similar issues. Fixing kpathsea config seems to be necessary, but the configuration seems to be somewhat distro-specific, and most of what I can find written on the topic is for other distros. I see several bug reports going back years with similairities:
https://bugs.gentoo.org/688200
https://bugs.gentoo.org/687866
Trying the perl-cleaner --reallyall suggestion next.
EDIT: perl-cleaner --reallyall completed, no change in outcome for failing to emerge dev-texlive/texlive-xetex-2019::gentoo and dev-tex/xmltex-1.9-r3::gentoo
Last edited by jeffk on Mon Apr 27, 2020 8:56 pm; edited 1 time in total |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1464
Location: Berlin, Germany
|
| Posted: Mon Apr 27, 2020 7:56 pm Post subject: |
|
|
I ended up asking the TUG list what it might be, and it turned out that my problem was that I had my path misconfigured. I had a path to my local texlive added to my path variable, and because of the weird way the texlive packages work, only some of the package was using that while the rest was trying to use the system path.
Double-check your .xsession, .bashrc, etc. files and make sure you don't have any texlive paths set there. I'm not sure if that's your problem, but maybe it'll help.
Cheers,
EE |
|
| Back to top |
|
|
jeffk
l33t
Joined: 13 Sep 2003
Posts: 671
|
| Posted: Mon Apr 27, 2020 8:57 pm Post subject: |
|
|
| ExecutorElassus wrote: | | Double-check your .xsession, .bashrc, etc. files and make sure you don't have any texlive paths set there. I'm not sure if that's your problem, but maybe it'll help. |
Thanks I appreciate the suggestion and will check it out. AFAIK I have not customized my user TeX environment. I normally install packaged texlive and use pdflatex via Org Mode export, with no further changes. |
|
| Back to top |
|
|
ununu
n00b
Joined: 19 Apr 2020
Posts: 31
|
| Posted: Thu Apr 30, 2020 12:12 pm Post subject: Texlive 2020 broken beyond repair |
|
|
| ExecutorElassus wrote: | I ended up asking the TUG list what it might be, and it turned out that my problem was that I had my path misconfigured. I had a path to my local texlive added to my path variable, and because of the weird way the texlive packages work, only some of the package was using that while the rest was trying to use the system path.
Double-check your .xsession, .bashrc, etc. files and make sure you don't have any texlive paths set there. I'm not sure if that's your problem, but maybe it'll help.
Cheers,
EE |
greetings, care to share the solution? |
|
| Back to top |
|
|
ununu
n00b
Joined: 19 Apr 2020
Posts: 31
|
| Posted: Thu Apr 30, 2020 12:14 pm Post subject: |
|
|
| John R. Graham wrote: |
One wild guess. Is this a prefix install?
Builds correctly here, by the way.
- John |
greets!
do you have any experience with prefix? is it hard to manually fix symlinks in the ebuild?
thanks |
|
| Back to top |
|
|
|
Portage & Programming
