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

[G. Branden Robinson]

Update of bug #63808 (project groff):

                Severity:             5 - Blocker => 3 - Normal             
                  Status:             In Progress => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #34:


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
ccessful 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 ec001d2a23a3b1740e8d004006c0fc0d7fb6e288
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 02:58:41 2023 -0600

    [build]: Detangle pdfroff, gropdf config (1/2).
    
    * 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.

commit 8316578166a73de1db05c555e640e9153ddc8d5d
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 11:55:02 2023 -0600

    [build]: Detangle pdfroff, gropdf config (2/2).
    
    * m4/groff.m4: Give pdfroff its own Autoconf macros to handle dependency
      checking, build objectives, and user notice.
    
      (GROFF_PDFROFF_DEPENDENCIES_CHECK): New macro requires
      `GROFF_AWK_PATH` and `GROFF_GHOSTSCRIPT_PATH`, determines whether
      pdfroff can be used at build time, and (if not) constructs part of
      message to be shown to user explaining why.
    
      (GROFF_PDFROFF_PROGRAM_NOTICE): New macro requires
      `GROFF_PDFROFF_DEPENDENCIES_CHECK` and emits message if needed.
    
      (GROFF_GHOSTSCRIPT_AVAILABILITY_NOTICE): Drop mention of impact on
      pdfroff since its dedicated notice covers this now.
    
    * configure.ac: Call the new macros at appropriate times.  Produce a new
      Automake macro, `USE_PDFROFF`, to replace inapposite use of
      `USE_GROPDF` in pdfmark.am.
    
    * contrib/pdfmark/pdfmark.am: Use `USE_PDFROFF` instead of `USE_GROPDF`.

commit 1ebdadc467436efb22ccf3c0dafef6a512a04914
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 13:42:51 2023 -0600

    [build]: Uninstall more fastidiously.
    
    Try to remove the configured PDF documentation directory in the event it
    is empty, but do not fail if it isn't.  (It can be a directory shared
    with other groff components; we don't know in what order the uninstall
    targets will serialize, but the last one run should succeed.)
    
    * contrib/mom/mom.am (uninstall_mom):
    * contrib/pdfmark/pdfmark.am (uninstall-pdfmark-hook):
    * contrib/sboxes/sboxes.am (uninstall_sboxes):
    * doc/doc.am (uninstall-pdf): Do it.

commit 206dcc0806b4da9d9d197540f4fa3aa86274d28b
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 14:30:45 2023 -0600

    [gropdf]: Recognize more URW file names.
    
    * font/devpdf/Foundry.in: Recognize URW foundry replacements for
      Helvetica Bold-Oblique and Helvetica Oblique under the file names
      "NimbusSans-BoldItalic.t1" and "NimbusSans-Italic.t1", respectively.

commit 6e001a7f397438d7f09e97155b3c1ec89c1fc855
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Feb 18 16:44:08 2023 -0600

    [gropdf]: Bifurcate test of font availability.
    
    * font/devpdf/tests/check-default-foundry.sh: Bifurcate test of font
      availability.  The Ghostscript executable can be present in the host
      environment without any Type 1 fonts.  The PDF standard requires that
      its base 14 be present in the renderer, so groff font descriptions for
      those 14 fonts (plus groff's "EURO" font) should always be available.
      But the remaining fonts from the "Base 35" PostScript level 2 set
      won't necessarily be, and so their font descriptions won't be, either.
      Skip the test rather than failing it in that case, because the
      Ghostscript executable can have any number of fonts built-in (in
      "%rom%" as "gs -h" puts it).  We'll need a more sophisticated Autoconf
      test to discern this scenario from a true failure case.


Typescript of four successful build scenarios (with and without Ghostscript
and URW fonts) attached.

(file #54381)

    _______________________________________________________

Additional Item Attachment:

File name: typescript-gbr-groff-1.23.0.rc2.88-6e00.txt Size:586 KB
   
<https://file.savannah.gnu.org/file/typescript-gbr-groff-1.23.0.rc2.88-6e00.txt?file_id=54381>



    _______________________________________________________

Reply to this item at:

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

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