[#87847] undefined symbol: mjit_init_p — Leam Hall <leamhall@...>

I pulled Ruby trunk on 3 Jul and am now getting errors similar to the

10 messages 2018/07/07

[#88088] [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention — normalperson@...

Issue #14937 has been reported by normalperson (Eric Wong).

9 messages 2018/07/24

[ruby-core:87852] Re: undefined symbol: mjit_init_p

From: Benoit Daloze <eregontp@...>
Date: 2018-07-07 17:09:13 UTC
List: ruby-core #87852
One more reason for https://bugs.ruby-lang.org/issues/13620 maybe? ;)
The number of ugly hacks because people don't want to "make install'
by default is huge IMHO :(

BTW, Ruby can be configured to install to a prefix writable by the
user and not only root:
./configure --prefix=~/prefix/ruby-trunk
for instance. Then there is no need to run anything as root.

On Sat, Jul 7, 2018 at 6:13 PM, Takashi Kokubun <takashikkbn@gmail.com> wrote:
> As I told you, `make install` is needed to make Ruby work. Running
> `make check` before `make install` is totally wrong with current
> trunk. Don't run `make check` before `make install`.
> 2018年7月8日(日) 0:57 Leam Hall <leamhall@gmail.com>:
>>
>> Thank you for a fast response.
>>
>> My process is to run 'make', and then 'make check' as a user and then
>> run 'make install' as root. The error comes from the 'make check' log.
>>
>> What's the best way to test ruby once it is fully built and installed?
>>
>> Again, thank you.
>>
>> Leam
>>
>>
>> On 07/07/2018 11:33 AM, Takashi Kokubun wrote:
>> > It's not reproducible on my environment and any CI since mjit_init_p
>> > does not exist anywhere in the current trunk, but my guess is that you
>> > didn't execute `make install` and thus you're using an old MJIT
>> > header. MJIT never works without `make install`.
>> >
>> > I always build ruby with `make all install` for that reason.
>> > 2018年7月8日(日) 0:23 Leam Hall <leamhall@gmail.com>:
>> >>
>> >> I pulled Ruby trunk on 3 Jul and am now getting errors similar to the
>> >> following:
>> >>
>> >> MJIT warning: failure in loading code from
>> >> '/tmp/_ruby_mjit_p20781u0.so': /tmp/_ruby_mjit_p20781u0.so: undefined
>> >> symbol: mjit_init_p
>> >>
>> >> The pull before that was 4 June and I didn't get the errors. It looks
>> >> like this commit may have removed mjit_init_p:
>> >>
>> >> https://github.com/ruby/ruby/commit/06f54f03039c225c5c0b5d1709865fb4fff02776#diff-75b3ed34ab948aab8de703d073f34a98
>> >>
>> >> I'm not sure what's referencing the lack of the symbol.
>> >>
>> >> Platform:
>> >>          CentOS 6, patched
>> >>          GCC from rpm,  4.4.7 20120313 (Red Hat 4.4.7-23) (GCC)
>> >>          Autoconf 2.69
>> >>
>> >> Thoughts?
>> >>
>> >> Leam
>> >>
>> >> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
>> >> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>> >
>> > Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
>> > <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>> >
>>
>
> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread