bug-groff
[Top][All Lists]
Advanced

[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: Sun, 26 Feb 2023 12:43:28 -0500 (EST)

Follow-up Comment #68, bug #63808 (project groff):

[comment #64 comment #64:]
> 
> ...things look much better in the contrived "scenario 01" (gs present, urw
absent).
It is only contrived for debian based distros, others include the ghostscript
fonts as supplied from github.

I think you may have missed the minor issue below.
> 
> $ ./configure --prefix=$HOME
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> ...
> checking for gs... gs
> checking for pnmcrop... found
> checking for pnmcut... found
> checking for pnmtopng... found
> checking for pnmtops... found
> checking for psselect... missing
> checking for URW fonts in Type 1/PFB format... none found
> checking whether pnmtops accepts the '-nosetpage' option... yes
> checking whether make defines 'RM'... yes
> checking for a diff program that supports option -D... yes
> checking whether test supports option -ef... yes
> checking for bash... /usr/bin/bash
> checking for gs version with good left sidebearing handling... got 9.53.3
(buggy)
> checking whether we are using the GNU C Library >= 2.1 or uClibc... (cached)
yes
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating test-groff
> config.status: creating src/include/config.h
> config.status: executing depfiles commands
> 
> GNU roff version 1.23.0.rc3.29-34dd52
> ----------------------------------------------------------------------
>  installation directory prefix    : /home/branden
>  C++ compiler and options         : g++ -g -O2 
>  use libgroff's memory allocator  : no
>  C compiler and options           : gcc -g -O2
>  Perl interpreter version         : 5.32.1
>  X11 support                      : disabled
>  'groff -l' uses print spooler    : no
>  use URW fonts for PDF output     : no
>  preconv can use uchardet library : no
>  can build groff.dvi, groff.pdf   : no
>  tests can use poppler PDF tools  : no
> ----------------------------------------------------------------------
> configure: Buggy version of Ghostscript detected.
> 
>   Ghostscript versions 9.00 <= x < 9.54 suffer from a rendering glitch
>   that affects the AT&T troff (and groff) special character '\(lh'; see
>   <https://bugs.ghostscript.com/show_bug.cgi?id=703187>.  If your
>   version of Ghostscript has not been patched to fix this problem, you
>   may need to work around it in groff documents you render for the
>   PostScript (and, for tbl(1) tables, HTML) output devices.
>   
> configure: URW fonts in Type 1/PFB format were not found.
> 
>   groff font description files for the URW fonts, used by the 'gropdf'
>   output driver, will not be available.  Use and embedding of fonts from
>   the 'U' foundry in PDF documents generated by groff will not be
>   possible.
> 
>   You can obtain the URW base 35 fonts from their GitHub project.  As of
>   this writing (2023-02-15), you can find them in the 'fonts' directory
>   of the following archives (choose one).
> 
>     https://github.com/ArtifexSoftware/urw-base35-fonts/archive/refs/
>       tags/20200910.zip
>     https://github.com/ArtifexSoftware/urw-base35-fonts/archive/refs/
>       tags/20200910.tar.gz
> 
>   You may wish to check for a newer release.
> 
>     https://github.com/ArtifexSoftware/urw-base35-fonts/releases
> 
>   By default, groff will look for these fonts in the search path shown
>   by the 'gs -h' command (if available) and in several directories
>   specified in font/devpdf/Foundry.in).  You will need to 'make
>   distclean' and re-run the 'configure' script after installing these
>   fonts.
> 
>   Alternatively, you can pass the option '--with-urw-fonts-dir=DIR'
>   to 'configure' to look for them in the directory DIR you specify.
>   If found, the 'U' foundry will be available via the '-y' option to
>   'gropdf' (accessed via the 'groff' command with the option '-P -y').
>     
> configure: The uchardet library was not found.
> 
>   The 'preconv' preprocessor program will be unable to attempt automatic
>   inference of an input file's character encoding.  See the preconv(1)
>   man page.
>   
> configure: The program 'psselect' was not found in $PATH.
> 
>   Consequently, groff's HTML output driver, 'grohtml', will not work
>   properly.  It will not be possible to prepare or install
>   groff-generated documentation in HTML format.
> 
> $ make check
>   GEN      lib/alloca.h
>   GEN      lib/inttypes.h
>   GEN      lib/limits.h
> ...
> PASS: contrib/rfc1345/tests/rfc1345-smoke-test.sh
>   GEN      font/devpdf/tests/check-default-foundry.sh
> SKIP: font/devpdf/tests/check-default-foundry.sh

As you stated this was a test for scenario 01 (gropdf in standard mode) I
would expect a complete default foundry and that check-default-foundry.sh
would pass but it looks like it was skipped.

Another issue is the configure missing urw-fonts message mentions that the
paths mentioned in gs -h are searched but I believe you have now removed this
from configure (correctly).

>   GEN      font/devpdf/tests/check-urw-foundry.sh
> SKIP: font/devpdf/tests/check-urw-foundry.sh
> SKIP: src/devices/grotty/tests/basic_latin_glyphs_map_correctly.sh
> PASS: src/devices/grotty/tests/osc8_works.sh
> ...
>
============================================================================
> Testsuite summary for GNU roff 1.23.0.rc3.29-34dd52
>
============================================================================
> # TOTAL: 163
> # PASS:  153
> # SKIP:  8
> # XFAIL: 2
> # FAIL:  0
> # XPASS: 0
> # ERROR: 0
>
============================================================================
> 



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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