[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #51003] "test-groff" can't find doc-macros in the "tmac/mdoc" direc
From: |
G. Branden Robinson |
Subject: |
[bug #51003] "test-groff" can't find doc-macros in the "tmac/mdoc" directory |
Date: |
Tue, 13 Nov 2018 23:46:10 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Update of bug #51003 (project groff):
Status: None => Need Info
Assigned to: None => gbranden
_______________________________________________________
Follow-up Comment #5:
I think actually Bjarni was right here. Scrubbing those pointless mdoc/
prefixes from the arguments to the .mso calls makes it straightforward to just
run groff (even a system groff) on the built groff_mdoc.7 with the macros from
the build.
This works for out-of-tree builds:
groff -t -M build/tmac -mdoc build/tmac/groff_mdoc.7 2>&1 >/dev/null
And in-tree ones:
groff -t -M tmac -mdoc tmac/groff_mdoc.7 2>&1 >/dev/null
This happens to fix the test-groff case with no extra effort.
./build/test-groff -t -mdoc ./build/tmac/groff_mdoc.7 2>&1 > /dev/null # out
of tree
./test-groff -t -mdoc ./tmac/groff_mdoc.7 2>&1 > /dev/null # in tree
Now, the question that really animates me is why .mso wasn't screaming to
stderr when it couldn't find mdoc/whatever. It's supposed to; I was just
hacking on input.cpp:macro_source() the other day. But that's a separate
bug.
Proposed fix attached. Ingo, please comment if you have a moment.
(file #45421)
_______________________________________________________
Additional Item Attachment:
File name: 51003.diff Size:0 KB
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?51003>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #51003] "test-groff" can't find doc-macros in the "tmac/mdoc" directory,
G. Branden Robinson <=