Description of problem: In order to build Rubinius (https://github.com/rubinius/rubinius), it just run `ldd /usr/bin/ruby` (https://github.com/rubinius/rubinius/blob/d19e086d013e7a3c99ec935ca84825db6f437dd8/configure#L1357-L1359) in order to determine the libc file name. Unfortunately, /usr/bin/ruby is not an executable, but a bash script installed by rubypick. This causes the ldd command to fail, thus preventing Rubinius from compiling. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. yum install wget gcc gcc-c++ automake flex bison ruby-devel rubygems rubygem-rake llvm-devel zlib-devel libyaml-devel openssl-devel gdbm-devel readline-devel ncurses-devel 2. wget -O rubinius-release-2.0.0-rc1.tar.gz https://github.com/rubinius/rubinius/archive/release-2.0.0-rc1.tar.gz 3. tar -xzvf rubinius-release-2.0.0-rc1.tar.gz 4. cd rubinius-release-2.0.0-rc1/ 5. ./configure Actual results: Checking for libc version: libc not found. Use the --libc configure option. libc not found. Use the --libc configure option. Please check configure.log for more details. Expected results: Success Additional info:
This has been fixed in rubinius 2.2.0.
What was changed? Can't see any difference in lines of you have referenced originally.
Actually, you are correct. I just tested rubinius-2.2.5's ./configure script with rubypick-1.1.1-1.fc19 and ruby-2.0.0.353-16.fc9: ./configure ... Checking for libc version: libc not found. Use the --libc configure option. Running 'configure' failed. Please check configure.log for more details.
Bump. This is still an issue and no one has responded to my points in #1065150. Is there a conflict of interest here? Vit Ondruch also appears to maintain rubypick. https://github.com/bkabrda/rubypick/commits/master
Have you considered to reported this issue to Rubinius? As far as I understand, usage of rbenv will suffer the same issues.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.