Re: Use script to test build configurations

"Kevin J. McCarthy" <[email protected]> Fri, 19 Jun 2026 13:21:09 +0800

Newsgroups	gmane.mail.mutt.devel
Message-ID	<[email protected]>

On Mon, Jun 01, 2026 at 09:17:55AM +0200, Rene Kita wrote:
>I kept the differences as they were in the build manifests.  The
>differences come from 7932020f (Fix freebsd build on srht., 2020-12-28)
>and me copying the FreeBSD configuration to OpenBSD.  We can investigate
>and clean this up later.
>
>I also added another stage which builds with -flto.  In my experience
>this can catch some errors with code shared between TUs.  I also added
>-O2 to CFLAGS to make sure the compiler runs some optimization stages
>which is needed to generate certain warnings.
>
>I kept the script in .builds.  As we have some more scripts which are
>aimed at developers it might be a good idea to create some dev directory
>to collect all the scripts.  If we get some consensus here I can add a
>commit for this and send a v2.
>
>I kept the commit which Oswald thinks is redundant.  While I generally
>agree, in that case the intent is to give a summary of the code so that
>I don't have to decipher the sed statement when skimming the code.  I'm
>open to removing it depending on the mood here, though.

I've applied these two to the stable branch and merged it over to 
master, so keep our sr.ht files in sync between the branches (until 
there is a reason to have them diverge).

Note that some time in the past couple week, build dependencies have 
changes for OpenBSD and Arch, and I haven't had a chance to track down 
why yet.

If you have the chance to take a look, go ahead, otherwise I'll try to 
figure out what needs to be fixed this coming week.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

signature.asc (application/pgp-signature, 833 B)