Follow-up Comment #6, bug #68597 (group groff): Thanks for this. Just a thought, can you check where groff is sourcing s.tmac from:-
derij@pip:~/groff-git/groff/build (master) $ strace -f -e trace=file groff
-pet -ms doc/ms.ms -z 2>&1 | grep "/s.tmac"
[pid 115228] openat(AT_FDCWD, "/home/derij/s.tmac", O_RDONLY) = -1 ENOENT (No
such file or directory)
[pid 115228] openat(AT_FDCWD, "/usr/local/lib/groff/site-tmac/s.tmac",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 115228] openat(AT_FDCWD, "/usr/local/share/groff/site-tmac/s.tmac",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 115228] openat(AT_FDCWD, "/usr/local/share/groff/1.25.0/tmac/s.tmac",
O_RDONLY) = 3
You can see it has looked in 3 directories before finding it in the
.../1.25.0/tmac directory. With your groff I would expect "/usr/local/" to be
replaced with "/home/mojo/.local". If you can run the above command on your
system I'm expecting it found s.tmac somewhere other than
/home/mojo/.local/share/groff/1.25.0/tmac/. If it has then an 'ls -l' will
show if its a good-un. If not delete it and try the pdfmom command below.
The reason 'test-groff' "works", is because it sets GROFF_TMAC_PATH to a
directory with a good s.tmac. and this is searched first, before the baked-in
directories created by configure. The definition in troff(1) is:-
GROFF_TMAC_PATH
A list of directories in which to search for macro files. troff
will scan directories given as
arguments to any specified -M options before these, then the
current directory (only if in un‐
safe mode), the user’s home directory, a site‐specific
directory (/usr/local/share/groff/
site-tmac), and a standard location
(/usr/local/share/groff/1.25.0/tmac) after them.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68597>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
