Bug 2183119

Summary: FTBFS with autoconf 2.72/2.73
Product: [Fedora] Fedora Reporter: Frédéric Bérat <fberat>
Component: ImageMagickAssignee: Luya Tshimbalanga <luya_tfz>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: blaise, davide, epel-packagers-sig, fedora, luya_tfz, michel, ngompa13, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-02-16 06:38:13 UTC Type: Bug
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: 2143303    

Description Frédéric Bérat 2023-03-30 12:41:00 UTC
Autoconf 2.72 (or 2.73) seems to be under preparation upstream, I therefore started to build dependent components against the pre-release [1] to verify that they can be built once it lands in Fedora.

Your component fails to build with the new version of autoconf, due to the following error:

configure:12004: error: possibly undefined macro: _AC_SYS_LARGEFILE_MACRO_VALUE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
error: Bad exit status from /var/tmp/rpm-tmp.pu3o1j (%build)


Unfortunately, this can't be fixed with an autoreconf, an update of the files provided by gnulib are necessary.
These files are usually added during the bootstrap of the source code, which is done to generate the release tarball.

Please forward this to the community, and update the component accordingly.

[1] https://lists.gnu.org/archive/html/autoconf/2023-03/msg00020.html

Comment 1 Frédéric Bérat 2024-02-16 06:38:13 UTC
This issue seems to have been fixed (not reproduced in latest mass prebuild of autocnf 2.72). Closing.