From: Ferenc Fejes <ferenc@fejes.dev>
To: Akira Yokosawa <akiyks@gmail.com>, perfbook@vger.kernel.org
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
Leonardo Bras <leobras.c@gmail.com>
Subject: Re: [RFC PATCH 0/7] Add reflowable HTML and EPUB3 build target
Date: Wed, 18 Nov 2026 04:55:54 +0100 [thread overview]
Message-ID: <ceea81feffcb33c0749230e9b0bd8ed555027514.camel@fejes.dev> (raw)
In-Reply-To: <6a18ce59-d2b2-4397-8d8a-f55b11d7b309@gmail.com>
Hi,
On Tue, 2026-11-17 at 18:44 +0900, Akira Yokosawa wrote:
> On 11/17/26 11:41, Akira Yokosawa wrote:
> > Hi,
> >
> > On 11/17/26 02:21, Ferenc Fejes wrote:
> > > On Mon, 2026-11-16 at 13:41 +0900, Akira Yokosawa wrote:
> > [...]
> >
> > > > That said, I couldn't complete "make epub" with
> > > > debian/testing's TeX
> > > > Live.
> > >
> > > Sorry for that, I'm using Debian unstable which is a little bit
> > > ahead
> > > of tasting. I compiled it on Ubuntu 26.04 as well, but AFAIR
> > > there I
> > > have to install lwrap from source.
> >
> > Tested "make html" under debian/unstable. It aborts with:
> >
> > ------------
> > [...]
> > LATEX=pdflatex sh utilities/runlwarp.sh perfbook-epub html
> > pdflatex -draftmode for perfbook-epub # lwarp wrapper generation
> > pdflatex -draftmode for perfbook-epub_html # HTML pass 1
> > ----- glossary generation failed for perfbook-epub_html -----
> > make: *** [Makefile:701: perfbook-epub_html.html] Error 2
> > ------------
> >
> > So, build_glossary in runlwarp.sh returned error.
> >
> > Can't you reproduce it?
Unfortunately I cannot reproduce it. It builds cleanly both on my
machine and with a small docker build I put together. Its a bit
complicated because I dont wanted to install and configure docker on my
machine, nor put an alternative texlive on to my disk. But feel free to
use only the docker file and build the image with docker, if you have
it installed already.
Here I use podman, the script grab a pre-built binary from github,
build the dockerfile to a debian:unstable container then build the epub
target. It works within the /tmp folder, I put here the content of
both file s/verbatim:
Dockerfile.debian-unstable
FROM docker.io/library/debian:unstable
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates locales tzdata && \
localedef -i en_US -c -f UTF-8 en_US.UTF-8 && \
rm -rf /var/lib/apt/lists/*
ENV LANG=en_US.utf8
RUN apt-get update && apt-get install -y --no-install-recommends \
fig2ps inkscape xfig graphviz psutils \
texlive-publishers texlive-pstricks texlive-science texlive-fonts-
extra \
texlive-latex-extra texlive-lang-japanese tex-gyre xindy \
make git gnuplot-nox time poppler-utils librsvg2-bin pandoc unzip
zip \
fontconfig fonts-freefont-ttf fonts-dejavu-core fonts-liberation &&
\
rm -rf /var/lib/apt/lists/*
COPY steel-city-comic.regular.ttf /usr/local/share/fonts/
RUN fc-cache /usr/local/share/fonts/
WORKDIR /work
CMD ["/bin/bash"]
And the build script (which also have a clean argument to delete the
whole image, containers etc.). Again, this is optional, makes things
easier if you dont have docker installed and do not want to install for
this experiment.
#!/usr/bin/env bash
# SPDX-License-Identifier: GPL-2.0-or-later
#
# Build perfbook EPUB inside a disposable rootless Debian unstable
Podman
# container, keeping podman-static, container storage, and the build
tree
# under /tmp (tmpfs) to avoid writing to SSD.
#
# Usage: ./docker/build-epub-podman.sh [branch] [make-target]
# ./docker/build-epub-podman.sh clean
# Defaults: branch=epub-rfc, make-target=epub
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
BRANCH="${1:-epub-rfc}"
TARGET="${2:-epub}"
PODMAN_BASE="/tmp/podman-static/podman-linux-amd64"
PODMAN_BIN="$PODMAN_BASE/usr/local/bin/podman"
BUILD_DIR="/tmp/perfbook-build"
IMAGE_NAME="perfbook-debian-unstable"
export
PATH="$PODMAN_BASE/usr/local/bin:$PODMAN_BASE/usr/local/lib/podman:$PAT
H"
export XDG_CONFIG_HOME="/tmp/podman-cfg"
export XDG_DATA_HOME="/tmp/podman-data"
export XDG_RUNTIME_DIR="/tmp/podman-run"
export TMPDIR="/tmp/podman-tmp"
export CONTAINERS_CONF="$XDG_CONFIG_HOME/containers/containers.conf"
export CONTAINERS_POLICY="$XDG_CONFIG_HOME/containers/policy.json"
export
CONTAINERS_REGISTRIES_CONF="$XDG_CONFIG_HOME/containers/registries.conf
"
if [ "$BRANCH" = "clean" ]; then
echo "==> Cleaning up /tmp podman and build artifacts..."
if [ -x "$PODMAN_BIN" ]; then
"$PODMAN_BIN" --root=/tmp/podman-root --
runroot="$XDG_RUNTIME_DIR" \
unshare rm -rf /tmp/podman-root "$XDG_RUNTIME_DIR"
"$XDG_DATA_HOME" 2>/dev/null || true
fi
rm -rf /tmp/podman-static /tmp/podman-root "$XDG_RUNTIME_DIR" \
"$XDG_CONFIG_HOME" "$XDG_DATA_HOME" "$TMPDIR" "$BUILD_DIR"
echo "==> Clean complete."
exit 0
fi
if [ ! -x "$PODMAN_BIN" ]; then
echo "==> Downloading and configuring podman-static in /tmp..."
mkdir -p /tmp/podman-static /tmp/podman-root "$XDG_RUNTIME_DIR" \
"$XDG_CONFIG_HOME/containers" "$XDG_DATA_HOME" "$TMPDIR"
curl -fsSL
"https://github.com/mgoltzsche/podman-static/releases/latest/download/podman-linux-amd64.tar.gz
" \
| tar -xz -C /tmp/podman-static
else
mkdir -p /tmp/podman-root "$XDG_RUNTIME_DIR" \
"$XDG_CONFIG_HOME/containers" "$XDG_DATA_HOME" "$TMPDIR"
fi
cp -r "$PODMAN_BASE/etc/containers/"* "$XDG_CONFIG_HOME/containers/"
cat <<EOF >> "$CONTAINERS_CONF"
helper_binaries_dir = ["$PODMAN_BASE/usr/local/lib/podman",
"$PODMAN_BASE/usr/local/bin"]
EOF
PODMAN=("$PODMAN_BIN" --root=/tmp/podman-root --
runroot="$XDG_RUNTIME_DIR")
echo "==> Cloning repository ($BRANCH -> $BUILD_DIR)..."
rm -rf "$BUILD_DIR"
git clone --no-hardlinks --branch "$BRANCH" "$REPO_ROOT" "$BUILD_DIR"
echo "==> Building Debian unstable container image ($IMAGE_NAME)..."
"${PODMAN[@]}" build \
-t "$IMAGE_NAME" \
-f "$SCRIPT_DIR/Dockerfile.debian-unstable" \
"$SCRIPT_DIR"
echo "==> Running make -j$(nproc) $TARGET in container..."
"${PODMAN[@]}" run --rm \
-v "$BUILD_DIR:/work" \
-w /work \
"$IMAGE_NAME" \
make -j"$(nproc)" "$TARGET"
echo "==> Done: $BUILD_DIR/perfbook.epub"
> >
> > >
> > > >
> > > > In perfbook-epub_html.log, there are a couple of warnings from
> > > > lwarp
> > > > as follows:
> > > >
> > > > -----
> > > > (/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty
> > > > Package: fancyvrb 2026/08/13 4.7 verbatim text (tvz,hv)
> > > > \FV@CodeLineNo=\count416
> > > > \FV@InFile=\read5
> > > > \FV@TabBox=\box69
> > > > \c@FancyVerbLine=\count417
> > > > \FV@StepNumber=\count418
> > > > \FV@OutFile=\write7
> > > > )
> > > >
> > > > Package lwarp Warning: A definition has changed:
> > > > (lwarp) fancyvrb: \FV@ListProcessLine
> > > > (lwarp) (9A9947A55E3D6D1C92E99F16EDC0BC68)
> > > > (lwarp) on input line 118.
> > > > -----
> >
> > I might have been confused by this warning. This "Warning" is
> > actually an "Info"-level message from lwarp, isn't it?
> >
> > > >
> > > > , and at the bottom of the log:
> > > >
> > > > --------------------------------
> > > > Package verifycommand Warning: Definitions have changed.
> > > > Patches for the following macros may need to be updated.
> > > > See the previous warnings for line numbers.
> > > >
> > > > Syntax: Patching pkg -> Defining pkg: Macro (checksum)
> > > > -----
> > > > (verifycommand) lwarp -> fancyvrb: \FV@ListProcessLine
> > > > (9A9947A55E3D6D1C92E99F16EDC0BC68)
> > > > -----
> > > > Look for updates to these packages.
> > > > --------------------------------
> >
> > I have no idea if this warning from verifycommand can be ignored
> > ...
> >
> > In the log under debian/stable, this warning looks like this:
>
> I meant debian/unstable
>
> Akira
I still concerned about why not build cleanly on your env. Cant you
have some local modifications/patches in the latex packages provided by
debian?
Oh and here is my fork to make things easier:
https://github.com/SPYFF/perfbook/tree/epub-rfc
Best,
Ferenc
next prev parent reply other threads:[~2026-11-18 3:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 21:01 [RFC PATCH 0/7] Add reflowable HTML and EPUB3 build target Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 1/7] reflow.ltx: Add LaTeX-to-HTML shims for lwarp builds Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 2/7] utilities: Add EPUB3 post-processor and stylesheet Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 3/7] utilities/runlwarp.sh: Add lwarp and Pandoc build driver Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 4/7] Makefile, .gitignore: Add epub and html build targets Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 5/7] epub: Add endnote variant for readers without popup footnotes Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 6/7] FAQ-BUILD.txt: Document HTML and EPUB build targets Ferenc Fejes
2026-11-15 21:01 ` [RFC PATCH 7/7] docker, gitlab-ci: Add EPUB build dependencies and CI job Ferenc Fejes
2026-11-16 4:41 ` [RFC PATCH 0/7] Add reflowable HTML and EPUB3 build target Akira Yokosawa
2026-11-16 17:21 ` Ferenc Fejes
2026-11-17 2:41 ` Akira Yokosawa
2026-11-17 9:44 ` Akira Yokosawa
2026-11-18 3:55 ` Ferenc Fejes [this message]
2026-11-18 10:32 ` Akira Yokosawa
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=ceea81feffcb33c0749230e9b0bd8ed555027514.camel@fejes.dev \
--to=ferenc@fejes.dev \
--cc=akiyks@gmail.com \
--cc=leobras.c@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.