[bug #63808] configure gives incorrect information regarding pdf generation

[G. Branden Robinson]

Update of bug #63808 (project groff):

                  Status:             In Progress => Need Info              

    _______________________________________________________

Follow-up Comment #25:

I've made some changes attempting to reflect the most recent discussions.


commit 38570563840748c7ae5a0a5c1514a9f0b1fdf91a
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 01:37:28 2023 -0600

    [gropdf]: Revise tests to be foundry-focussed.
    
    * font/devpdf/tests/basic-fonts-present.sh: Stop trying to match font
      descriptions in the "devps" directory with ones in "devpdf"; instead,
      test whether "BuildFoundries" did its job.  Test for font descriptions
      corresponding to the full 35 PostScript Level 2 font repertoire, plus
      groff's "EURO".
    
    * font/devpdf/tests/urw-fonts-present.sh: Drop stale comment and rename
      variable for better parallelism with the other test above.
    
    Continues <https://savannah.gnu.org/bugs/?63808>.  Thanks to Deri James
    for the continued discussion.

commit 00b5b3803332abe0557c54b1cf8f5b78baf1329b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 01:41:29 2023 -0600

    [gropdf]: Rename tests.
    
    ...to more accurately characterize their purpose.
    
    * font/devpdf/tests/basic-fonts-present.sh:
    * font/devpdf/tests/urw-fonts-present.sh: Rename these...
    
    * font/devpdf/tests/check-default-foundry.sh:
    * font/devpdf/tests/check-urw-foundry.sh: ...to these.
    
    * font/devpdf/devpdf.am (font_devpdf_TESTS): Reflect rename.

commit e3954e5b15ae956c2ee7f98c8f323bfa9172e5a3
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 02:04:00 2023 -0600

    [gropdf]: Don't test if hobbled.
    
    [gropdf]: Don't run automated tests if 'gropdf' will be operating with
    reduced function.  If neither Ghostscript nor the URW fonts are
    available at configuration time, there is no point testing for
    successful build-time population of the font descriptions for the
    default and URW foundries.
    
    * font/devpdf/devpdf.am (font_devpdf_TESTS) [USE_GROPDF]: Run
      "check-default-foundry" only if gropdf is fully functional.
    
      (font_devpdf_TESTS) [USE_GROPDF && HAVE_URW_FONTS]: Run
      "check-urw-foundry" only if the URW fonts were found.
    
    Continues <https://savannah.gnu.org/bugs/?63808>.  Thanks to Deri James
    for the continued discussion.

commit 03640de878b4b362bce18af6bea008bd4d2bb3be
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 02:50:51 2023 -0600

    [build]: Rename GROFF_CHECK_GROPDF_PROGRAMS macro.
    
    [build]: Rename `GROFF_CHECK_GROPDF_PROGRAMS` macro to
    `GROFF_GROPDF_DEPENDENCIES_CHECK` to generalize for greater accuracy in
    forthcoming change.
    
    * configure.ac:
    * m4/groff.m4: Do it.

commit 9f91b87d4d4ab9d762ac9b87e8a8ba526dff9a82 (HEAD -> master)
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 02:58:41 2023 -0600

    [build]: Revise gropdf configuration.
    
    * m4/groff.m4 (GROFF_GROPDF_DEPENDENCIES_CHECK): Add `AC_REQUIRE`ment on
      `GROFF_URW_FONTS_CHECK`.  Per discussion with Deri James, if _either_
      Ghostscript or the URW fonts are avilable, gropdf will be fully
      functional, consequent to commit d5515, 22 June.  Drop dependency on
      awk; it is used only at configuration time (in an Autoconf macro) and
      since Savannah #62775 was resolved (19 September), it has not been
      strictly necessary.  (It is useful for searching more locations for
      URW fonts, but several others are searched even if it is absent.)
      Stop populating notice text here, instead moving it...
    
      (GROFF_GROPDF_PROGRAM_NOTICE): ...here, since it no longer needs to be
      dynamically constructed.
    
    Continues <https://savannah.gnu.org/bugs/?63808>.  Thanks to Deri James
    for the continued discussion.


I'm attaching a shell session transcript of builds in all 4 scenarios
discussed.  Locate each one by searching for the word "scenario" in the text
file.

I got expected errors from gropdf when building in scenario 00 (no URW, no
Ghostscript).


/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/addftinfo/addftinfo.1:
warning: unable to embed font file for 'Times-Italic' (TI) (issing entry in
'download' file?)
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/addftinfo/addftinfo.1:
warning: unable to embed font file for 'Times-Roman' (TR) (mssing entry in
'download' file?)
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/addftinfo/addftinfo.1:
warning: unable to embed font file for 'Helvetica-Bold' (HB)(missing entry in
'download' file?)
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/addftinfo/addftinfo.1:
warning: unable to embed font file for 'Times-Bold' (TB) (mising entry in
'download' file?)
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/afmtodit/afmtodit.1:
warning: unable to embed font file for 'Courier-Oblique' (CI) missing entry in
'download' file?)
fonts_x.roff: listing font 'ABI'...                                      
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/utils/afmtodit/afmtodit.1:
warning: unable to embed font file for 'Courier' (CR) (missingentry in
'download' file?)
fonts_n.roff: listing font 'ABI'...                                      
fonts_x.roff: listing font 'AI'...                                       
fonts_n.roff: listing font 'AI'...                                       
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:contrib/chem/chem.1:
warning: unable to embed font file for 'Symbol' (S) (missing entry in
'dwnload' file?)


But two real problems are evident:

1. pdfroff dies hard (and crashes the build) if Ghostscript is not available. 
This was predictable; I've known for a long time that pdfroff produces
PostScript documents and then used gs to make PDF from them.  This is an
Autoconf usage problem; pdfroff has been hiding behind generic "PDF" macros
(or even gropdf-specific ones).  Fixing this should be a minor matter of
writing a notice macro similar to the one gropdf has.  We know that pdfroff
has a hard dep on both awk _and_ Ghostscript.

2. I got a gropdf error I do not understand the cause of in scenario 10 (with
URW, without Ghostscript).


/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:contrib/glilypond/glilypond.1:
warning: unable to embed font file for 'Helvetica-BoldOblique'(HBI) (missing
entry in 'download' file?)
/home/branden/BUILD/groff-1.23.0.rc2.84-9f91b/gropdf:src/devices/gropdf/gropdf.1:
warning: unable to embed font file for 'Helvetica-Oblique' (HI) missing entry
in 'download' file?)


It's just for these 2 man pages (out of about 60), and only for these fonts. 
Where do you suggest I start?

(file #54377)

    _______________________________________________________

Additional Item Attachment:

File name: groff-build-log.gbr.2023-02-18.txt Size:420 KB
   
<https://file.savannah.gnu.org/file/groff-build-log.gbr.2023-02-18.txt?file_id=54377>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63808>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/