[#104004] [Ruby master Feature#17883] Load bundler/setup earlier to make `bundle exec ruby -r` respect Gemfile — mame@...
Issue #17883 has been reported by mame (Yusuke Endoh).
21 messages
2021/05/24
[ruby-core:103968] [Ruby master Bug#17021] "arm64" and "arm" are mixed in RbConfig on Apple silicon
From:
nagachika00@...
Date:
2021-05-22 06:56:49 UTC
List:
ruby-core #103968
Issue #17021 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: REQUIRED to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: DONTNEED 43a9a974e276dc49b03ec81ccace0adb534a3d20 is included in ruby_3_0 branch. ---------------------------------------- Bug #17021: "arm64" and "arm" are mixed in RbConfig on Apple silicon https://bugs.ruby-lang.org/issues/17021#change-92101 * Author: watson1978 (Shizuo Fujita) * Status: Closed * Priority: Normal * ruby -v: ruby 2.8.0dev (2020-07-09T09:14:53Z master addbb7d16e) [arm64-darwin20] * Backport: 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: DONTNEED ---------------------------------------- When I checked the value of `RbConfig::CONFIG` on the Apple silicon macOS,e I found "arm64" and "arm" are mixed as following. ``` $ ruby -v ruby 2.8.0dev (2020-07-09T09:14:53Z master addbb7d16e) [arm64-darwin20] $ ruby -e 'require "rbconfig"; pp RbConfig::CONFIG' | grep "arm" "/Users/watson/.rbenv/versions/2.8.0/include/ruby-2.8.0/vendor_ruby/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/include/ruby-2.8.0/site_ruby/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/include/ruby-2.8.0/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/vendor_ruby/2.8.0/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/site_ruby/2.8.0/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/2.8.0/arm64-darwin20", "sitearch"=>"arm64-darwin20", "arch"=>"arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/include/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/include/arm64-darwin20", "sitearchlibdir"=>"/Users/watson/.rbenv/versions/2.8.0/lib/arm64-darwin20", "archlibdir"=>"/Users/watson/.rbenv/versions/2.8.0/lib/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/arm64-darwin20", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/arm64-darwin20", "Target: arm64-apple-darwin20.0.0\n" + "target_cpu"=>"arm64", "target"=>"arm64-apple-darwin20", "host_cpu"=>"arm", "host"=>"arm-apple-darwin20.0.0", "build_cpu"=>"arm", "build"=>"arm-apple-darwin20.0.0", "/Users/watson/.rbenv/versions/2.8.0/lib/ruby/2.8.0/arm64-darwin20", "topdir"=>"/Users/watson/.rbenv/versions/2.8.0/lib/ruby/2.8.0/arm64-darwin20"} ``` "target_cpu" indicates "arm64", however, "host_cpu" has "arm"... I'd like to know whether this behavior is the right thing. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>