Bug 1606143

Summary: ruby: FTBFS in Fedora rawhide
Product: [Fedora] Fedora Reporter: Mohan Boddu <mboddu>
Component: rubyAssignee: Vít Ondruch <vondruch>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mo, mtasaka, pvalena, s, strzibny, vanmeeuwen+fedora, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby-2.5.1-94.fc29 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-26 17:14:19 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: 1602938    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Mohan Boddu 2018-07-20 18:38:07 UTC 
ruby failed to build from source in Fedora rawhide

https://koji.fedoraproject.org/koji/taskinfo?taskID=28228587


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix ruby at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
ruby will be orphaned. Before branching of Fedora 30,
ruby will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Mohan Boddu 2018-07-20 18:38:17 UTC 
Created attachment 1467467 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Mohan Boddu 2018-07-20 18:38:21 UTC 
Created attachment 1467468 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Mohan Boddu 2018-07-20 18:38:28 UTC 
Created attachment 1467469 [details]
state.log
Comment 4 Vít Ondruch 2018-07-26 07:51:04 UTC 
This is the root cause:

~~~
$ cat CMakeLists.txt 
cmake_minimum_required(VERSION 2.6)
install (FILES test.txt DESTINATION bin)

$ cmake . -DCMAKE_INSTALL_PREFIX=/tmp/test_rubygems_15764/prefix
-- The C compiler identification is GNU 8.1.1
-- The CXX compiler identification is unknown
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error in CMakeLists.txt:
  No CMAKE_CXX_COMPILER could be found.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.


-- Configuring incomplete, errors occurred!
See also "/tmp/test_rubygems_15764/ext/CMakeFiles/CMakeOutput.log".
See also "/tmp/test_rubygems_15764/ext/CMakeFiles/CMakeError.log".
~~~

The question is if we should have gcc-c++ available or not. I still think we should not need it and it would be better to fix/disable this particular test, but OTOH:

https://bugs.ruby-lang.org/issues/14590