Requiring newer autoconf for X.Org packages?

Keith Packard keithp at keithp.com
Tue Aug 30 22:40:02 UTC 2022


Alan Coopersmith <alan.coopersmith at oracle.com> writes:

> But currently we leave it mostly up to whoever builds the tarballs for release
> to decide what version of autoconf to use (though they in turn mostly rely on
> what their distro builder packages in the version they run), and even the latest
> xorg-server-21.1.4 tarball was built with autoconf 2.69.

Yeah, GCC still uses 2.69 internally, Debian stable ships with 2.69, if
I were shipping a generated configure script, I'd be tempted to use that
too.

> If not, we could start bumping the AC_PREREQ to 2.70 in just the repos that
> use reallocarray, to ensure we don't accidentally ship versions that can't
> build on NetBSD - that's still a small subset of the modules we ship - only
> 11 out of 265 so far:

Is there something keeping us from just adding _OPENBSD_SOURCE somewhere
in xorg-macros.m4 and have the affected repos use that?

-- 
-keith
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.x.org/archives/xorg-devel/attachments/20220830/f6993cc7/attachment.sig>


More information about the xorg-devel mailing list