Update of bug #66085 (group groff):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #6:
[comment #5 comment #5:]
> If it's happening only on my system, is the build somehow picking
> up my $HOME/bin/mv despite claiming to use /bin/mv? Or is it for
> some reason giving /bin/mv the -i option in the Makefile? Either
> of those seems mildly buggy.
I have an answer to this: it turns out "/bin/mv" is output on stderr even when
the command initially run is $HOME/bin/mv. This makes sense, as whichever
command is launched, ultimately /bin/mv is called to do the actual work.
So the Makefile is using $HOME/bin/mv rather than the system's mv to move
files. This still feels mildly buggy, but if so, is a gnulib issue rather
than a groff one, as comment #4 points out. So closing this ticket.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66085>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
