From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <foss+yocto@0leil.net>, <docs@lists.yoctoproject.org>
Cc: "Quentin Schulz" <quentin.schulz@cherry.de>
Subject: Re: [PATCH v4 0/3] migrate Debian/Ubuntu to pip packages for docs + fix epub and latexpdf targets not finding glob images
Date: Mon, 16 Feb 2026 15:26:50 +0100 [thread overview]
Message-ID: <DGGGFO6KUB95.16VEII2QZY3MJ@bootlin.com> (raw)
In-Reply-To: <20260216-fix-make-multi-target-v4-0-749e588cb7f5@cherry.de>
Hi,
I have an issue after applying the series:
$ ./documentation/tools/build-docs-container almalinux:9 latexpdf
[...]
latexmk -pdf -dvi- -ps- 'theyoctoproject.tex'
make[1]: latexmk: No such file or directory
make[1]: *** [Makefile:28: theyoctoproject.pdf] Error 127
make[1]: Leaving directory '/docs/documentation/_build/latex'
make: *** [Makefile:53: latexpdf] Error 2
make: Leaving directory '/docs/documentation'
You reported an error with latexpdf on IRC, was that it?
Antonin
next prev parent reply other threads:[~2026-02-16 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:26 [PATCH v4 0/3] migrate Debian/Ubuntu to pip packages for docs + fix epub and latexpdf targets not finding glob images Quentin Schulz
2026-02-16 11:26 ` [PATCH v4 1/3] use a venv for installing packages with pip Quentin Schulz
2026-02-18 8:18 ` [docs] " Antonin Godard
2026-02-23 17:33 ` Quentin Schulz
2026-02-24 8:28 ` Antonin Godard
2026-02-24 12:52 ` Quentin Schulz
2026-02-24 13:55 ` Quentin Schulz
2026-02-24 14:03 ` Antonin Godard
2026-02-16 11:26 ` [PATCH v4 2/3] consistently use pip packages for all distros Quentin Schulz
2026-02-16 11:26 ` [PATCH v4 3/3] convert SVGs to PDF and PNG using sphinxcontrib.rsvgconverter plugin Quentin Schulz
2026-02-16 14:26 ` Antonin Godard [this message]
2026-03-02 9:53 ` [PATCH v4 0/3] migrate Debian/Ubuntu to pip packages for docs + fix epub and latexpdf targets not finding glob images Antonin Godard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGGGFO6KUB95.16VEII2QZY3MJ@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=foss+yocto@0leil.net \
--cc=quentin.schulz@cherry.de \
/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