Bug 1943007 - ceph: FTBFS with upcoming autoconf-2.71
Summary: ceph: FTBFS with upcoming autoconf-2.71
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: ceph
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1942967
TreeView+ depends on / blocked
 
Reported: 2021-03-25 12:42 UTC by Ondrej Dubaj
Modified: 2021-03-26 11:25 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-03-26 11:25:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ondrej Dubaj 2021-03-25 12:42:23 UTC
Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test

Comment 1 Kaleb KEITHLEY 2021-03-26 11:25:14 UTC
autoconf-2.71 works fine for me on three machines: f35/rawhide, f34/rawhide (pre-branch), f34 post-branch.

E.g.:

$ rpm -q autoconf
autoconf-2.71-1.fc34.noarch

$ rpmbuild -ba SPECS/ceph.spec
...
+ /usr/bin/rm -rf /home/kkeithle/rpmbuild/BUILDROOT/ceph-16.1.0-0.8.snapshot.fc34.x86_64
+ RPM_EC=0
++ jobs -p
+ exit 0


1) ceph doesn't use autoconf (see the .spec file ;-))
2) your copr build's build.log.gz is truncated
3) ceph builds take a lot of disk and memory. In all likelihood your builds failed because of one of those issues, not because of the new autoconf.

And as another data point, I can remove autoconf entirely (and install libtool with `rpm -i --nodeps libtool-2.4.6-40.fc34.x86_64.rpm`) and build successfully.

I strongly suggest you configure your copr builds with more disk (~50G is what I have found to be needed, YMMV) and 12G memory minimum.


Note You need to log in before you can comment on or make changes to this bug.