From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: LaTeX: Need help with packaging a book in GNU Guix
Date: Tue, 29 Aug 2023 20:55:42 +0200 [thread overview]
Message-ID: <878r9toez5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871qflemc6.fsf@gmail.com> (Artyom V. Poptsov's message of "Tue, 29 Aug 2023 21:26:49 +0300")
"Artyom V. Poptsov" <poptsov.artyom@gmail.com> writes:
> Hello Nicolas!
> Thanks, that worked out indeed. I've added other LaTeX packages as
> well, searching by the required ".sty" files.
Great!
> /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh: /gnu/store/05770yhxad3d3p4q7rgw8clh0y1gi5sc-texlive-glossaries-66594/bin/makeglossaries: /usr/bin/env: bad interpreter: No such file or directory
> make: *** [Makefile:77: make_glossary] Error 1
> make: *** Waiting for unfinished jobs....
> --8<---------------cut here---------------end--------------->8---
>
>
> It looks like "makeglossaries" cannot find "/usr/bin/env" program.
It should be fixed on master, if you can guix pull again.
> Strangely enough when I add "texlive" to the inputs, the problem is
> gone.
This is not strange. `texlive' provides `perl' once in its inputs, and
all scripts, such as `makeglossaries', have their shebang line updated.
In modular TeX Live, packages are responsible for their own script(s);
and need to provide `perl', for example, as an input. This is not
obvious when the script has no extension, as it is the case here.
Regards,
next prev parent reply other threads:[~2023-08-29 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 3:51 LaTeX: Need help with packaging a book in GNU Guix Artyom V. Poptsov
2023-08-29 9:01 ` Nicolas Goaziou
2023-08-29 12:42 ` Artyom V. Poptsov
2023-08-29 12:47 ` Nicolas Goaziou
2023-08-29 18:26 ` Artyom V. Poptsov
2023-08-29 18:55 ` Nicolas Goaziou [this message]
2023-08-29 19:19 ` Artyom V. Poptsov
2023-08-31 18:00 ` Artyom V. Poptsov
2023-09-01 3:15 ` Artyom V. Poptsov
2023-09-01 5:24 ` Dr. Arne Babenhauserheide
2023-09-01 8:26 ` Andreas Enge
2023-09-01 10:58 ` Nicolas Goaziou
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r9toez5.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=help-guix@gnu.org \
--cc=poptsov.artyom@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 read-only IMAP folder(s) and NNTP newsgroup(s).