[Top][All Lists]

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

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

From: Deri James
Subject: [bug #63808] configure gives incorrect information regarding pdf generation
Date: Thu, 16 Feb 2023 20:29:12 -0500 (EST)

Update of bug #63808 (project groff):

                  Status:                   Fixed => Need Info              
             Open/Closed:                  Closed => Open                   


Follow-up Comment #12:

I have had to re-open this bug since my testing has shown some problems. First
I will describe my testing method (in case there is something wrong with it).
I want to do 4 separate runs after doing a git pull, a make distclean and rm
-rf build (all runs will be out of tree builds with the distclean and the rm
between each run).

The four runs will be to test presence/absence of ghostscript and the URW

Absense of ghostscript is achieved by renaming /usr/bin/gs to ogs.

Absence of URW font is achieved by renaming /usr/share/fonts/default/Type1 to
oType1 (this is the location of my URW fonts, your location may differ but the
principle is the same).

Each run (from the build directory, after ghostscript/URW have been adjusted
to be present/absent) is:-

[copy results of configure to a log file]
make -j4
ls font/devpdf
[copy to log to show which fonts/foundries are available]
ls doc
[copy to log to show if pdf documentation has been produced]
make check
[copy summary to log]

The four logs are attached.

The problem lies in the URW only run (no ghostscript). Configure detects no
ghostscript but reports that gropdf is in base 14 fonts modeonly and then make
produces no pdf documentation. The log shows there are 71 fonts available for

You used to have a test basic-fonts-present.sh which tested for 35 fonts plus
EURO but you have now changed it to 14 fonts plus EURO. You said because you
got failures when testing with a ghostscript only run. This is a real failure,
so it is better to investigate why fonts are missing than change the test to
pass when something is wrong! Please can you provide the output of gs -h and
an ls of whichever directory actually holds the postscript fonts. (Ghostscript
may have changed the font names once again!). As you can see in my log of a
ghostscript only run all 35 fonts are present in devpdf, as they should be, if
they are not it is a real error.

I think you mentioned using chroot for your tests, please make sure the paths
given by gs -h are available at wherever you have chrooted to.

You say:

    * font/devpdf/devpdf.am: Test availability of "basic" (PDF base
      14) fonts (plus groff's "EURO") if either Ghostscript or URW fonts are
      available.  Test availability of URW fonts (35) only if Ghostscript
      _and_ the URW fonts were found at configuration time.

The correct logic is this:-

if gs or urw
    run basic check
    if urw
        run urw check

I don't see why the urw check is only run if both gs and urw are present! The
U- foundry has no no dependency on ghostscript at all. If you really want belt
and braces you could rename the current basic-fonts-present.sh to
base14-fonts-present.sh, and resurect the previous incarnation, and extend the
logic to:-

if gs or urw
    run basic check
    if urw
        run urw check
    run base14 check

(file #54363, file #54364, file #54365, file #54366)


Additional Item Attachment:

File name: URW and GS.log                 Size:2 KB
    <https://file.savannah.gnu.org/file/URW and GS.log?file_id=54363>

File name: URW Only No GS.log             Size:3 KB
    <https://file.savannah.gnu.org/file/URW Only No GS.log?file_id=54364>

File name: No GS and No URW.log           Size:3 KB
    <https://file.savannah.gnu.org/file/No GS and No URW.log?file_id=54365>

File name: GS only.log                    Size:3 KB
    <https://file.savannah.gnu.org/file/GS only.log?file_id=54366>


Reply to this item at:


Message sent via Savannah

reply via email to

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