From: andras.bali@... Date: 2014-02-11T10:16:37+00:00 Subject: [ruby-core:60650] [ruby-trunk - Bug #9507] Ruby 2.1.0 is broken on ARMv5: tried to create Proc object without a block Issue #9507 has been updated by Andras Bali. I can only confirm this bug. Could we support anyhow in debugging this? ---------------------------------------- Bug #9507: Ruby 2.1.0 is broken on ARMv5: tried to create Proc object without a block https://bugs.ruby-lang.org/issues/9507#change-45084 * Author: _ _ * Status: Open * Priority: Normal * Assignee: Charlie Somerville * Category: core * Target version: current: 2.2.0 * ruby -v: ruby 2.1.0dev (2013-09-04 trunk 42822) [armv5tel-linux-eabi] * Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- I'm using Arch Linux ARM which currently ships with Ruby 2.1.0. On all my ARMv5 devices, trying to run Ruby fails with a strange error, which has also been reported here: https://github.com/archlinuxarm/PKGBUILDs/issues/705 ARMv6 and ARMv7 devices on the other hand seem to be fine. Using git-bisect I was able to determine that the first bad commit is 2f522b9cc6f3e184404040b12af4486520a73b26 (r42822), which implements #8426: [root@alarm ~]# ruby --version ruby 2.1.0dev (2013-09-04 trunk 42822) [armv5tel-linux-eabi] [root@alarm ~]# ruby -e 'puts "foo"' /usr/lib/ruby/2.1.0/rubygems/requirement.rb:26:in `lambda': tried to create Proc object without a block (ArgumentError) from /usr/lib/ruby/2.1.0/rubygems/requirement.rb:26:in `' from /usr/lib/ruby/2.1.0/rubygems/requirement.rb:18:in `' from /usr/lib/ruby/2.1.0/rubygems/specification.rb:10:in `require' from /usr/lib/ruby/2.1.0/rubygems/specification.rb:10:in `' from /usr/lib/ruby/2.1.0/rubygems.rb:1161:in `require' from /usr/lib/ruby/2.1.0/rubygems.rb:1161:in `' from /usr/lib/ruby/2.1.0/rubygems.rb:114:in `' from :1:in `require' from :1:in `' The previous commit works correctly: [root@alarm ~]# ruby --version ruby 2.1.0dev (2013-09-04 trunk 42821) [armv5tel-linux-eabi] [root@alarm ~]# ruby -e 'puts "foo"' foo The problem is still present in trunk (r44896). -- http://bugs.ruby-lang.org/