Follow-up Comment #12, bug #67612 (group groff): [comment #11 comment #11:] >>> Lacking a test-gropdf analogue to the test-groff script, running the >>> latest >>> gropdf directly is not straightforward. >>> >>> $ echo 'Yo!' | $HOME/groff/build/test-groff -Z -Tpdf | >>> $HOME/groff/build/gropdf >>> gropdf: fatal error: failed to open 'download' file >>> >>> >>> There's probably a way to make it work, but it's not worth my time to >>> figure out, since all I care about is "is it 0 or not-0?" >> >> Hmm. This works for me: >> >> >> $ echo 'Yo!' | ./build/test-groff -Z -Tpdf | ./build/gropdf >/dev/null >> $ echo $? >> 0 > > You may need "-F build/font" on the gropdf invocation, otherwise gropdf will > be using fonts in the current system directories, whereas groff (via > test-groff) uses the fonts in build/font.
Good point, but it doesn't change the outcome for me.
$ echo 'Yo!' | ./build/test-groff -Z -Tpdf | ./build/gropdf -F ./font -F
./build/font >/dev/null
$ echo $?
0
(Since I use separate source and build trees, I directed _gropdf_ to
both...though to be fair I don't see anything in the **source** _font/devpdf_
directory that the output driver can directly use.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
