Follow-up Comment #13, bug #67612 (group groff):

The GROFF_FONT_PATH setting in the test-groff you are using will cause troff
to use the fonts in build/font and the lack of a -F flag will cause gropdf to
use the system locations (probably /usr/local/share/groff) to find the fonts
and download file.

It has nothing to do with whether you build in or out of tree, without the
flag gropdf will be looking at a different font directory than troff does
(because the GROFF_FONT_PATH is not set in the environment in which gropdf
runs), Quite often this may "work" if you have a previous installed groff
version in /usr/local/share but if your previous groff is in /usr/share/groff
then gropdf will fail unless you have used --prefix=/usr when configure was
run - which is unlikely if you are simply building groff to test a recent
change, without intending to install it.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to