Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1999479

Summary: [F36FTBFS]: ruby fails to build from source in Fedora Rawhide
Product: [Fedora] Fedora Reporter: Ondrej Dubaj <odubaj>
Component: rubyAssignee: Jun Aruga <jaruga>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jaruga, joe, jprokop, mo, mtasaka, pvalena, ruby-packagers-sig, s, strzibny, vanmeeuwen+fedora, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-04 10:40:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1999534, 1936597, 1992484    

Description Ondrej Dubaj 2021-08-31 08:07:12 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: The easiest way to reproduce the problem is to execute a fedora scratch-build on your package. Thank you for cooperation!

Comment 1 Vít Ondruch 2021-09-08 15:01:23 UTC
This seems to be caused by the following commit:

Which removes the C compiler check. I have reported this issue upstream:

The simple workaround would be to add the `AC_PROG_CC` check back. Lets give upstream some time to come up with the right solution.

Comment 2 Ondrej Dubaj 2021-09-09 07:18:08 UTC
Can we maybe revert the changes in the given commit and test if it solves our issue ?

Comment 3 Jun Aruga 2021-09-29 13:13:06 UTC
> Can we maybe revert the changes in the given commit and test if it solves our issue ?

I am not sure if the reverting the changes works. But here is a comment mentioned on the upstream. The following patch by using the `./` instead of `autoconf`, and adding the `g++` compiler works to pass the `./configure` with autoconf 2.71. Now another issue is if we really require a C++ compiler to build Ruby, as Vit asked on the upstream ticket. The C++ compiler was not required previously.

diff --git a/ruby.spec b/ruby.spec
index 414eb19..c5c6edc 100644
--- a/ruby.spec
+++ b/ruby.spec
@@ -188,6 +188,7 @@ BuildRequires: procps
 %{?with_hostname:BuildRequires: %{_bindir}/hostname}
 BuildRequires: multilib-rpm-config
 BuildRequires: gcc
+BuildRequires: gcc-c++
 BuildRequires: make
 BuildRequires: zlib-devel
@@ -619,7 +620,7 @@ rm -rf ext/fiddle/libffi*
 cp -a %{SOURCE3} .
 %configure \
         --with-rubylibprefix='%{ruby_libdir}' \

Comment 4 Jun Aruga 2021-09-30 14:53:43 UTC
The upstream patch is here now. Vit, could you apply it? Thanks.

Comment 5 Jun Aruga 2021-10-01 12:37:18 UTC
I sent the PR to fix the FTBFS.

Comment 6 Jun Aruga 2021-10-04 10:40:04 UTC
FTBFS by autoconf was fixed by .

Note that FTBFS still happens on rawhide (f36) due to OpenSSL 3.0 dependency. But this can be another topic. So, I would close this ticket.