[#100689] [Ruby master Feature#17303] Make webrick to bundled gems or remove from stdlib — hsbt@...
Issue #17303 has been reported by hsbt (Hiroshi SHIBATA).
11 messages
2020/11/02
[#100852] [Ruby master Feature#17326] Add Kernel#must! to the standard library — zimmerman.jake@...
SXNzdWUgIzE3MzI2IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGpleiAoSmFrZSBaaW1tZXJtYW4pLg0K
24 messages
2020/11/14
[#100930] [Ruby master Feature#17333] Enumerable#many? — masafumi.o1988@...
Issue #17333 has been reported by okuramasafumi (Masafumi OKURA).
10 messages
2020/11/18
[#101071] [Ruby master Feature#17342] Hash#fetch_set — hunter_spawn@...
Issue #17342 has been reported by MaxLap (Maxime Lapointe).
26 messages
2020/11/25
[ruby-core:101007] [Ruby master Bug#17021] "arm64" and "arm" are mixed in RbConfig on Apple silicon
From:
nobu@...
Date:
2020-11-21 13:36:08 UTC
List:
ruby-core #101007
Issue #17021 has been updated by nobu (Nobuyoshi Nakada). Eregon (Benoit Daloze) wrote in #note-7: > Should another RbConfig::CONFIG key be used? Which one? Usually we use target_* instead. ---------------------------------------- Bug #17021: "arm64" and "arm" are mixed in RbConfig on Apple silicon https://bugs.ruby-lang.org/issues/17021#change-88676 * Author: watson1978 (Shizuo Fujita) * Status: Open * Priority: Normal * ruby -v: ruby 2.8.0dev (2020-07-09T09:14:53Z master addbb7d16e) [arm64-darwin20] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- 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>