[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>
Issue #18465 has been reported by ioquatix (Samuel Williams).
16 messages
2022/01/09
[#107150] [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically — "ko1 (Koichi Sasada)" <noreply@...>
Issue #18494 has been updated by ko1 (Koichi Sasada).
4 messages
2022/01/17
[#107170] Re: [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically
— Eric Wong <normalperson@...>
2022/01/17
> https://bugs.ruby-lang.org/issues/18494
[#107302] [Ruby master Bug#18553] Memory leak on compiling method call with kwargs — "ibylich (Ilya Bylich)" <noreply@...>
Issue #18553 has been reported by ibylich (Ilya Bylich).
4 messages
2022/01/27
[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>
Issue #18557 has been reported by mame (Yusuke Endoh).
18 messages
2022/01/29
[ruby-core:107224] [Ruby master Bug#18504] configure prints a warning when cross-compiling
From:
"shyouhei (Shyouhei Urabe)" <noreply@...>
Date:
2022-01-21 08:50:48 UTC
List:
ruby-core #107224
Issue #18504 has been updated by shyouhei (Shyouhei Urabe). I know what is going on. About the only thing we can do is to settle for that warning. It works nonetheless. The problem is our `--with-gcc=` configure option. That way you can instruct which compiler to use. Then we have to find the right linker that understands proper link-time optimisation scheme that the user-input compiler employs. In case of cross compilation autoconf also sets `$CC`. But from our point of view there is no way to tell if that `aarch64-linux-gnu-gcc` value was user-input or auto-genrated. We have to do the same thing (find the linker that comes with the compiler), which eventually succeeds, with a warning. In order to suppress the warning we have to detect where the `$CC` value came from; which is impractical. Please just live with the annoyance, or give up `--with-gcc`. ---------------------------------------- Bug #18504: configure prints a warning when cross-compiling https://bugs.ruby-lang.org/issues/18504#change-96085 * Author: mame (Yusuke Endoh) * Status: Assigned * Priority: Normal * Assignee: shyouhei (Shyouhei Urabe) * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- ``` $ sudo apt-get install gcc-aarch64-linux-gnu $ ./configure --host=aarch64-linux-gnu downloading config.guess ... done downloading config.sub ... done checking build system type... x86_64-pc-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking target system type... aarch64-unknown-linux-gnu checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc checking for aarch64-linux-gnu-aarch64-linux-gnu-ld... no checking for aarch64-linux-gnu-ld... aarch64-linux-gnu-ld configure: WARNING: using cross tools not prefixed with host triplet ``` It attempts to find `aarch64-linux-gnu-aarch64-linux-gnu-ld`, which fails. Then it finds `aarch64-linux-gnu-ld`, but also it prints "WARNING: using cross tools not prefixed with host triplet". I guess this was triggered by commit:2c96e04868477eaa1420945d57bf5b3adb521e84. @shyouhei Could you take a look? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>