commit 845c063cf6d0370bc53b0182d234e4f7a32c796f
parent d14a326051e921e9b6b99326adfd744d45e1aff0
Author: aabacchus <ben@bvnf.space>
Date: Wed, 28 Dec 2022 20:22:40 +0000
blog: typo
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/blog/008-sudo-make-install.html b/blog/008-sudo-make-install.html
@@ -20,7 +20,7 @@
<p>But when I was trying to compile some documents, the neatpdf PDF postprocessor couldn't find the requested fonts and it looked all wrong with weird or no fonts. Everything was installed in <code>$(BASE)</code> correctly. I could compile the same document in the git source directory and get the right results, so it had to be something to do with the way in which contents of files are changed for being used from <code>$(BASE)</code>.</p>
-<p>The font definitions contain a line <code>fontpath /path/to/font</code> so that PDFs know where to find the fonts. This is written to using a sed call. Neatroff was meant to only be used from the source dir, so font files usually say <code>fontpath $(PWD)/fonts</code>, where <code>$(PWD)</code> hopefully refers to the toplevel source directory (ie. you're running <code>make install</code> not <code>make -f ../Makefile install</code>.</p>
+<p>The font definitions contain a line <code>fontpath /path/to/font</code> so that PDFs know where to find the fonts. This is written to using a sed call. Neatroff was meant to only be used from the source dir, so font files usually say <code>fontpath $(PWD)/fonts</code>, where <code>$(PWD)</code> hopefully refers to the toplevel source directory (ie. you're running <code>make install</code> not <code>make -f ../Makefile install</code>).</p>
<p>To permit installing neatroff to the system, the sed call changes <code>fontpath $(PWD)/fonts</code> to <code>fontpath $(BASE)/fonts</code>:</p>
<pre><code>@for f in "$(BASE)/devutf"/*; do \
