Project

General

Profile

Actions

Bug #22472

closed

Both yjit & zjit break ruby 4.0.9 build on x86_64

Bug #22472: Both yjit & zjit break ruby 4.0.9 build on x86_64

Added by satadru (Satadru Pramanik) 5 days ago. Updated 3 days ago.

Status:
Third Party's Issue
Assignee:
-
Target version:
-
ruby -v:
ruby 4.0.7 (2026-09-15 revision 229531a6cf) +PRISM [x86_64-linux]
[ruby-core:127234]

Description

I see this error building ruby 4.0.9 with --enable-yjit on x86_64 with our Chromebrew builds.

Here is the error with RUST_BACKTRACE=full:

transdb.h updated linking miniruby
thread '' (41405) panicked at src/input_files.rs:1954:35: called Option::unwrap() on a None value stack backtrace:
0: 0x5fb9dbc3e571 - 1: 0x5fb9dbc53a3a - 2: 0x5fb9dbc43ddc -
3: 0x5fb9dbc1c246 - 4: 0x5fb9dbc368e1 - 5: 0x5fb9dbc36c42 -
6: 0x5fb9dbc1c324 - 7: 0x5fb9dbc15099 -
8: 0x5fb9dbc1ce6d - 9: 0x5fb9dbc5416c -
10: 0x5fb9dbc54132 - 11: 0x5fb9dbc53ee9 -
12: 0x5fb9db8ba26f - 13: 0x5fb9db8b6ab7 -
14: 0x5fb9db9047ff - 15: 0x5fb9db92840c -
16: 0x5fb9db9fe566 - 17: 0x5fb9db928633 - 18: 0x5fb9db9fe566 - 19: 0x5fb9db928633 -
20: 0x5fb9db9284d4 -
21: 0x5fb9db9284d4 -
22: 0x5fb9db9fe566 - 23: 0x5fb9db9a5ace - 24: 0x5fb9dbbea37f -
25: 0x5fb9dbbe99ed -
26: 0x5fb9dbbeb44a -
27: 0x5fb9dbbe6fed -
28: 0x5fb9dbc3dcd9 - 29: 0x7aa62c1e6f84 -
30: 0x7aa62c123b3f - __clone 31: 0x0 -
collect2: fatal error: ld terminated with signal 6 [Aborted], core dumped

Updated by satadru (Satadru Pramanik) 4 days ago Actions #1 [ruby-core:127237]

  • Subject changed from Enabling yjit breaks ruby 4.0.9 build on x86_64 to Both yjit & zjit break ruby 4.0.9 build on x86_64

Using --disable-yjit and --disable-zjit fixes the build.

Updated by alanwu (Alan Wu) 3 days ago Actions #2 [ruby-core:127241]

  • Status changed from Open to Third Party's Issue

This is not an issue with ruby but with the tool chain you're using to build ruby.

collect2: fatal error: ld terminated with signal 6 [Aborted], core dumped

The linker you're using is crashing, and it's not clear which linker you're using. In any case, you should report this to the tool chain maintainers.

Updated by satadru (Satadru Pramanik) 3 days ago Actions #3 [ruby-core:127243]

Thanks. I'm using mold 3.0 as our linker and this has been reported on the mold issue tracker already at https://github.com/rui314/mold/issues/1741 as affecting builds of ruby 4.0.7.

So this can be closed here.

Actions

Also available in: PDF Atom