Bug 1999490

Summary:	[F36FTBFS]: vmem fails to build from source in Fedora Rawhide
Product:	[Fedora] Fedora	Reporter:	Ondrej Dubaj <odubaj>
Component:	vmem	Assignee:	Adam Borowski <kilobyte>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	kilobyte
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-09 16:35:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1936597, 1992484

Description Ondrej Dubaj 2021-08-31 08:08:04 UTC

Your package fails to build with the newest autoconf-2.71, which was part of a recent wide Fedora change. More information about Fedora autoconf Change available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test. The easiest way to reproduce the problem is to execute a fedora scratch-build on your package. Thank you for cooperation!

Comment 1 Adam Borowski 2021-09-09 16:35:03 UTC

The problem was with glibc-2.34 (malloc_hook changes to be exact) rather than autoconf-2.71.

But, as this library's replacement, memkind, is not only vastly more powerful, but also as of version 1.12 has reached feature parity with what vmem did, there's no point spending developer tuits in fixing vmem.  Let's retire it.

On the other hand, vmem is still working well in releases of Fedora and Red Hat that have glibc ≤ 2.33.