Re: groff 1.25.0.rc1 testing

"G. Branden Robinson" <[email protected]> Sun, 19 Jul 2026 10:08:47 -0500
Newsgroups gmane.comp.printing.groff.general
Message-ID <20260719150847.2odqd7iclmufznbl@illithid>
--yjjdxqan5xtk7txy
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: groff 1.25.0.rc1 testing
MIME-Version: 1.0

Hi Alexis,

At 2026-07-19T10:38:35+0200, Alexis (surryhill) wrote:
> Testing this rc on macOS with nixpkgs I noticed the following changes:
>=20
> * The build fails with:
>=20
>   /nix/store/5vmd3cqj6skjajg0yj9jl8dsddwp0700-bash-5.3p9/bin/bash: \
>     line 35: ./soelim: No such file or directory
[...]
>=20
>         GEN      doc/line-layout.eps
>     make: *** [Makefile:20231: doc/line-layout.eps] Error 127

Thanks for the report.  I've fixed both of these and pushed the fixes to
Git.

>   It seems that new build dependencies on Ghostscript and ImageMagick
>   have been introduced for the $(DOC_LINE_LAYOUT_EPS): "target" in
>   doc/doc.am by use of the gs and convert commands.
>=20
>   Aside on convert: Depending on the version groff wants to require
>   newer versions of ImageMagick prefer use of the "new" `magick`
>   command over the "old" `convert` command.
>=20
>   While introducing new build time dependencies isn't an issue per se,
>   and Ghostscript has been a soft requirement for building groff for
>   quite some time, it seems it is now needed in build targets where
>   previously it was not.  Hence I'd like to suggest that these
>   additions/changes are communicated appropriately in the build
>   documentation and release notes=E2=80=94apologies if they already are a=
nd I
>   just missed the memo.

I _tried_ to keep the scope of the new build dependencies restricted to
"maintainer mode", but as groff wasn't using the `AM_MAINTAINER_MODE`
macro at all, my attempt was fruitless.

I now have groff using that macro, which requires a new `configure`
option for people building from Git, but no changes for distribution
archive users.

Here are the specific commits fixing each of these issues:

https://lists.gnu.org/archive/html/groff-commit/2026-07/msg00154.html
https://lists.gnu.org/archive/html/groff-commit/2026-07/msg00155.html

> Apart from the above minor issues the build for groff 1.25.0.rc1
> on nixpkgs (and therefore likely NixOS) succeeds, yay!

Excellent news!  Did you try "make check"?

> I'll continue testing the behaviour of groff 1.25.0.rc1 and report
> back in case of any oddities or regressions.

Thank you!  I'll keep my eyes peeled.

Regards,
Branden

--yjjdxqan5xtk7txy
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmpc6HcACgkQ0Z6cfXEm
bc4KmhAAg5xk49CfotPPmspnhKwLeSLXT6O+2pLfrLQaXpX4N/cVinQHa4CzySRi
EhruKGu2Md5t3/E547HsUzyh+u+J5d/GbJCSMLnH7Xd0v/Kr9t0HuxscKOryPD5C
US4YMPZmyAsk9c/uqOvh24Z2pAS9CeycvhzrGIGeC2T6HjDu5i/eIw7FCObtZkKA
BU2rf33gt0sk4AaTCTpscUyYMMLFLZ5orfHQGKH2w3iqkSzmy81sRNRkvHye/Bot
uGeXAzuyde7EQQ/ESjpocZl3aQPbrp1tx7Zw9wBFOh1N8f56ISJi6nNE9e8LxszN
nNblxR3fxvJWH93ZR4PecgHBViMx8rxhOy3iXbfMvTwfgu4CsQLUuHLgOzpnAfmL
w1wmpuguyDissAEkQ6S9PG4gCcswrx6V/Y8wsemDBVctUCN4uuwnNEgCE/30g9qE
hUD24uisie/6d+DEC1LWbXwCx8tvNVK3BkXl+fgR3cbER33Z3uf5zEGroNZCXOoR
hkOmzVpVYhmA1UifN1LyaSCdf4Gj5beX7ySGro79Otmj/E4PeKHL/Ar68NN/glUD
3uUKbjbwwvQTeJ7K5j28GkrK22iF/d+5IGcDRDERcUGsvk+J0OXuQyXmYPjmF/WN
Kl18hQpCh3WZBIUVZ0F2jbOnl9yx9s/+nGuhYNcGBtUDfx/5btA=
=6ZBe
-----END PGP SIGNATURE-----

--yjjdxqan5xtk7txy--