I'm trying to get pdflatex working on AWS Lambda and I've hit a roadblock. I believe I have the basic tex engine running as I'm able to run the command
pdflatex -version and get the correct information.
However, when I try to compile an actual latex file (
pdflatex sample.tex) I get the following error:
kpathsea: Running mktexfmt pdflatex.fmt mktexfmt: No such file or directory
Due to the ephemeral nature of AWS Lambda I created a new
bin/ folder, added it to the
$PATH and included in it all of the required dependencies as well as rebuild the
ls-R file at the root of the directory. The
ls-R file contains the location of
pdflatex.fmt but my guess is that it's not searching the correct directory for the
ls-R file. The
kpathsea documentation states you can set the default installation location in
$TEXMF but that doesn't seem to have worked.
$ echo $TEXMF /var/task/bin # the created bin directory
Any ideas on how to continue debugging this installation? Or if there's a better approach at this.
kpswhich pdflatex.fmtreturn nothing? What have you set
TEXMFto? Do you mean that you have
bin/? Do you not have
texmf.cnfsomewhere? I guess ... how familiar are you with TeX Live in other contexts?
kpswhich(I installed the texlive-scheme-basic if that changes anything). I don't have much familiarity with TeX Live in general other than the reading that I've been doing in the past couple of days (if you have any useful links I appreciate it). I realized that I hadn't modified the contents of
texmf.cnfto match the Lambda environment but that didn't change anything. I've updated the original question with the value of
$TEXMF. I'm not sure I get your question about
kpsewhich. At least, that's surprising.
kpsewhichis part of the
kpathseaTeX Live package. It is part of
collection-basicand classified as
mktexfmt? That looks to be missing too? You seem to be missing essential binaries or they are not found in your PATH.
kpswhich, but that is a typo. It should be