From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
Bjarni Ingi Gislason <bjarniig@simnet.is>,
linux-man@vger.kernel.org, groff@gnu.org
Subject: Re: groff build problem involving "ckd_mul" and "ckd_add"
Date: Mon, 06 Oct 2025 19:06:39 -0700 [thread overview]
Message-ID: <87frbvea8g.fsf@gmail.com> (raw)
In-Reply-To: <yp5rnfroyllwzxnigmpofdtpycr6fakcytpp2jof2upemftn63@kcpoibftbp7w>
Alejandro Colomar <alx@kernel.org> writes:
>> It builds for me and others, like Deri and Grisha Levit.
>>
>> https://lists.gnu.org/archive/html/groff/2025-10/msg00009.html
>>
>> Have you "bootstrapped" lately? That's necessary for Git users when we
>> bump the version of gnulib we include, which we probably did after
>> either 1.23.0.2695-49927 or 1.23.0.1254-19a18, and maybe both. One
>> thing I do recall is bumping gnulib to get at the checked arithmetic
>> functions--precisely the ones you see above.
>
> Yes, I bootstrapped today. I also ran 'git submodule update' prior to
> that.
>
>>
>> Also, FYI:
>>
>> $ git describe origin/master
>> 1.23.0-4017-g3ea378d35
>
> I can reproduce both on my server (Debian) and on my desktop (Devuan).
> I'm using Sid, so that may have something to do (maybe I have a more
> recent compiler that errors where yours doesn't?).
This was discussed and fixed in Gnulib a few months ago [1]. I assume
you are using g++ 15 and the others are not.
Here are the relevant commits:
$ git branch --contains=7ee6e40b6730c87e5c1323bb5c2564bcb6eff9e4
* master
stable-202507
$ git branch --contains=e331531a771443edae4135e6bcd016282cf1a3aa
* master
stable-202507
But groff is using a branch that does not contain them:
commit e3ff929ddea95e0fc9fe7ea3541d28665de42370
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Mar 28 03:10:49 2025 -0500
Commit: G. Branden Robinson <g.branden.robinson@gmail.com>
CommitDate: Sat Mar 29 22:27:32 2025 -0500
gnulib: Update stable/2025-01 branch.
...to commit 3fbc2c7bb3, 3 March.
Using the following command I can make ./bootstrap use the master branch
from my local checkout to copy files:
$ env GNULIB_SRCDIR=$HOME/.local/src/gnulib ./bootstrap
Allows me to build groff fine with g++ 15.
Collin
[1] https://lists.gnu.org/archive/html/bug-gnulib/2025-05/msg00207.html
next prev parent reply other threads:[~2025-10-07 2:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 18:17 '^\}$' is changed to a space character Bjarni Ingi Gislason
2025-09-30 18:46 ` Alejandro Colomar
2025-09-30 22:36 ` Bjarni Ingi Gislason
2025-10-01 6:49 ` Alejandro Colomar
2025-10-02 21:57 ` Bjarni Ingi Gislason
2025-09-30 19:40 ` G. Branden Robinson
2025-09-30 19:44 ` G. Branden Robinson
2025-10-02 22:25 ` Alejandro Colomar
2025-10-04 9:16 ` Alejandro Colomar
2025-10-04 9:42 ` G. Branden Robinson
2025-10-04 10:30 ` Alejandro Colomar
2025-10-05 13:48 ` '^\}$' is (not) " G. Branden Robinson
2025-10-05 18:47 ` Alejandro Colomar
2025-10-06 8:51 ` G. Branden Robinson
2025-10-06 10:25 ` Alejandro Colomar
2025-10-06 10:42 ` groff build problem involving "ckd_mul" and "ckd_add" G. Branden Robinson
2025-10-06 11:10 ` Alejandro Colomar
2025-10-07 2:06 ` Collin Funk [this message]
2025-10-07 8:47 ` Alejandro Colomar
2025-10-07 20:06 ` G. Branden Robinson
2025-10-07 20:24 ` Alejandro Colomar
2025-10-07 20:29 ` G. Branden Robinson
2025-10-07 21:10 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frbvea8g.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=alx@kernel.org \
--cc=bjarniig@simnet.is \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox