groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem building latest git source


From: G. Branden Robinson
Subject: Re: Problem building latest git source
Date: Thu, 7 Jul 2022 23:54:11 -0500

[content warning: this message is a bug hunt]

Hi Deri,

At 2022-07-07T16:30:43+0100, Deri wrote:
> On Thursday, 7 July 2022 05:48:33 BST G. Branden Robinson wrote:
> > Deri, can you throw any light on this stuff?
> 
> One possibility is that somehow it is running the currently installed
> groff, rather than test-groff, so it would be looking at the download
> file in /usr/share/groff/1.23.0/font/devpdf rather than the new
> download just created within the build directory.

This appears to be close.  When creating font/devpdf/download, we are at
pains to set up the $PATH.

However, neither this target nor BuildFoundries itself has a dependency
on "afmtodit", so BuildFoundries will happily run without it present at
all, or just as happily run the one on the system, which could be very
old.  (That's bad because I'd like to change afmtodit to no longer
require the map file as a mandatory operand.[1])

So I've just pushed some commits that do the following things.

1. Add this dependency of "BuildFoundries" on "afmtodit".
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=7e017781dbdcc3558303bc2191ee0da4e5cd026c

2. Add an option to BuildFoundries to treat these warnings about URW
   font generation as fatal.
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=645a371a568b2e2cd518ba5505eb69259af3d065

3. Have our Makefile pass the script that option.
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=5c91d9b64a0a4ac05df30e412391582948aad90d

There is another issue I've been hitting.  My builds still work fine in
my general-purpose development environment, but fail in my Debian
bullseye chroot with no optional dependencies _except_ the URW fonts.

With the added paranoia above, that build fails as follows.

  GEN      font/devpdf/download
BuildFoundries: notice: Copied grops font AB...
BuildFoundries: notice: Copied grops font ABI...
BuildFoundries: notice: Copied grops font ZD...
BuildFoundries: notice: Copied grops font EURO...
BuildFoundries: error: cannot locate AFM file for font 'U-AB'
make: *** [Makefile:14572: font/devpdf/download] Error 2

In this failing build tree, I added an ad hoc diagnostic to report the
search path.  I'll quote the directory detected by my configure script
and that output.

[...]
checking for URW fonts in Type 1/PFB format... found in 
/usr/share/fonts/type1/urw-base35/
[...]
BuildFoundries: notice: search path: 
:/usr/share/fonts/afm/gsfonts:/usr/share/fonts/default/Type1:/usr/share/fonts/default/afm/adobestd35:/usr/share/fonts/afm/urw-base35:/opt/local/share/fonts/urw-fonts:/usr/local/share/fonts/ghostscript:/usr/share/ghostscript/9.53.3/Resource/Init:/usr/share/ghostscript/9.53.3/lib:/usr/share/ghostscript/9.53.3/Resource/Font:/usr/share/ghostscript/fonts:/var/lib/ghostscript/fonts:/usr/share/cups/fonts:/usr/share/ghostscript/fonts:/usr/local/lib/ghostscript/fonts:/usr/share/fonts:/home/branden/BUILD/groff-1.23.0.rc1.2698-5c91d/font/devps:/home/branden/BUILD/groff-1.23.0.rc1.2698-5c91d/font/devps
BuildFoundries: error: cannot locate AFM file for font 'U-AB'

I observe that the detected directory,
/usr/share/fonts/type1/urw-base35/, is NOT making it into this search
path.  (/usr/share/fonts/afm/urw-base35 is close, but no cigar.)

But my Foundry file exists and _does_ have this directory in it.

$ grep urw-base35 font/devpdf/Foundry
foundry||:(gs):/usr/share/fonts/type1/gsfonts:/usr/share/fonts/default/Type1:/usr/share/fonts/default/Type1/adobestd35:/usr/share/fonts/type1/urw-base35:/opt/local/share/fonts/urw-fonts:/usr/local/share/fonts/ghostscript
foundry|U|:/usr/share/fonts/type1/gsfonts:/usr/share/fonts/default/Type1:/usr/share/fonts/default/Type1/adobestd35:/usr/share/fonts/type1/urw-base35:/opt/local/share/fonts/urw-fonts:/usr/local/share/fonts/ghostscript:(gs)

Is something perhaps wrong with the way BuildFoundries is reading these
data in?

Anyway, the directory sniffed out by 'configure' _does_ have AFM files
in it.

$ ls /usr/share/fonts/type1/urw-base35/*.afm | head
/usr/share/fonts/type1/urw-base35/C059-BdIta.afm
/usr/share/fonts/type1/urw-base35/C059-Bold.afm
/usr/share/fonts/type1/urw-base35/C059-Italic.afm
/usr/share/fonts/type1/urw-base35/C059-Roman.afm
/usr/share/fonts/type1/urw-base35/D050000L.afm
/usr/share/fonts/type1/urw-base35/NimbusMonoPS-Bold.afm
/usr/share/fonts/type1/urw-base35/NimbusMonoPS-BoldItalic.afm
/usr/share/fonts/type1/urw-base35/NimbusMonoPS-Italic.afm
/usr/share/fonts/type1/urw-base35/NimbusMonoPS-Regular.afm
/usr/share/fonts/type1/urw-base35/NimbusRoman-Bold.afm

So it looks to me like something got disconnected here.

Regards,
Branden

[1] https://savannah.gnu.org/bugs/?59284

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]