[Bug 242630] [PowerPC] lang/ruby26 build fails on rb_mjit_min_header-2.6.5.h (FreeBSD 12.1-RELEASE-p1)

[email protected]
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242630

Mark Millard <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #12 from Mark Millard <[email protected]> ---
(In reply to commit-hook from comment #10)

Context: cross building via ports-mgmt/poudriere-devel
on an old PowerMac G5. As seen from inside a jail for
the 32-bit powerpc world area poudriere uses:

JAILNAME      VERSION      ARCH              METHOD TIMESTAMP           PATH
FBSDpowerpc   13.0-CURRENT powerpc           null   2019-12-31 01:21:28
/usr/obj/DESTDIRs/clang-powerpc-installworld-poud

Based on -r522079 of ports in a head -r356187
based context (both the G5 and the system in
clang-powerpc-installworld-poud):

. . . (through linking miniruby) . . .
building .ext/include/powerpc-freebsd13/rb_mjit_min_header-2.6.5.h
./miniruby -I./lib -I. -I.ext/common  ./tool/transform_mjit_header.rb "cc "
rb_mjit_header.h .ext/include/powerpc-freebsd13/rb_mjit_min_header-2.6.5.h
*** Signal 6

Stop.
make[1]: stopped in /wrkdirs/usr/ports/lang/ruby26/work/ruby-2.6.5
*** Error code 1

In other words: the miniruby that it built crashes when it
is then used.

The backtrace shows a __stack_chk_fail during rb_vm_exec:

Program terminated with signal SIGABRT, Aborted.
#0  kill () at kill.S:4
4       kill.S: No such file or directory.
(gdb) bt
#0  kill () at kill.S:4
#1  0x41d7f648 in __fail (msg=<optimized out>) at
/usr/src/lib/libc/secure/stack_protector.c:128
#2  0x41d7f598 in __stack_chk_fail () at
/usr/src/lib/libc/secure/stack_protector.c:135
#3  0x01a25dac in rb_vm_exec (ec=0x41f51028, mjit_enable_p=1) at vm.c:1903
#4  0x01a25fa8 in rb_iseq_eval (iseq=0x41fe0890) at vm.c:2133
#5  0x018f2554 in rb_load_internal0 (ec=0x41f51028, fname=<optimized out>,
wrap=<optimized out>) at load.c:612
#6  0x018f3230 in rb_require_internal (fname=<optimized out>, safe=0) at
load.c:1029
#7  0x018f272c in rb_require_safe (fname=1107240840, safe=<optimized out>) at
load.c:1075
#8  rb_f_require (obj=<optimized out>, fname=1107240840) at load.c:821
#9  0x01a31938 in call_cfunc_1 (func=<optimized out>, recv=<optimized out>,
argc=<optimized out>, argv=<optimized out>) at ./vm_insnhelper.c:1755
#10 0x01a2b0e0 in vm_call_cfunc_with_frame (ec=0x41f51028, reg_cfp=0x41fdb708,
calling=<optimized out>, ci=0x442d3500, cc=<optimized out>) at
./vm_insnhelper.c:1908
#11 vm_call_cfunc (ec=0x41f51028, reg_cfp=0x41fdb708, calling=<optimized out>,
ci=0x442d3500, cc=<optimized out>) at ./vm_insnhelper.c:1924
#12 0x01a2a00c in vm_call_method_each_type (ec=<optimized out>, cfp=<optimized
out>, calling=<optimized out>, ci=<optimized out>, cc=<optimized out>) at
./vm_insnhelper.c:2245
#13 0x01a29e40 in vm_call_method (ec=0x41f51028, cfp=0x41fdb708,
calling=0xffffce20, ci=0x442d3500, cc=0x44348000) at ./vm_insnhelper.c:2400
#14 0x01a10384 in vm_call_general (ec=<optimized out>, reg_cfp=<optimized out>,
calling=<optimized out>, ci=<optimized out>, cc=<optimized out>) at
./vm_insnhelper.c:2417
#15 0x01a1337c in vm_exec_core (ec=0x41f51028, initial=<optimized out>) at
insns.def:765
#16 0x01a25cb8 in rb_vm_exec (ec=0x41f51028, mjit_enable_p=1) at vm.c:2104
#17 0x01a260d8 in rb_iseq_eval_main (iseq=<optimized out>) at vm.c:2144
#18 0x0189b2c4 in ruby_exec_internal (n=0x41ff8080) at eval.c:262
#19 ruby_exec_node (n=<optimized out>) at eval.c:326
#20 0x0189b0d4 in ruby_run_node (n=<optimized out>) at eval.c:318
#21 0x018146ec in main (argc=<optimized out>, argv=<optimized out>) at
./main.c:42

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.