Follow-up Comment #4, bug #68908 (group groff):

At 2026-11-14T11:58:48-0500, Dave wrote:
> Follow-up Comment #2, bug #68908 (group groff):
> [comment #1 comment #1:]
>> If you commit whatever changes you've made and rebootstrap,
>> this problem should go away.
> I'm willing to take your word for it.  But this step has never been
> necessary in the past (I've used maybe five git commands, and "commit"
> isn't one of them), and a dirty build environment shouldn't change the
> roff-language semantics of a numeric register.

In a dirty build environment, _anything_ might go wrong.  One can inject
errors into the source code in countless ways.  Essentially all bets are
off, and assuming that "make" with the default target succeeds, the only
way we can have confidence in the result is to run "make check"
afterwards.

"make distcheck" is even better.

Another alternative is to discard all the changes in your working copy,
then rebootstrap.  If you don't want to lose those changes, stash them
first.


$ git stash -m 'my temporary experiments'
$ git checkout .
$ ./bootstrap




    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to