# Beware prelink and compiling ruby from source

**URL:** <https://www.ruby-forum.com/t/beware-prelink-and-compiling-ruby-from-source/185030>\
**Category:** Ruby\
**Created:** [March 12, 2010, 2:07am UTC](https://www.ruby-forum.com/t/beware-prelink-and-compiling-ruby-from-source/185030 "2010-03-12T02:07:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/e495f1/32.png) [@dougal](https://www.ruby-forum.com/u/dougal)\
**Post date:** [March 12, 2010, 2:07am UTC](https://www.ruby-forum.com/t/beware-prelink-and-compiling-ruby-from-source/185030/1 "2010-03-12T02:07:32Z")

</div>

All,

Putting this in the ruby-talk ML just to have it searchable in case  
others  
run into this problem.

On some redhat based distros, if you compile ruby 1.9.1 from source and  
install it as /usr/bin/ruby and have the “prelink” rpm installed, the  
ruby  
binary can become corrupted by prelink. When you try to run the  
interpreter  
after prelink has run against it, you get a c stack trace with this  
error  
message:

ruby: [BUG] iseq\_compile\_each: unknown node: NODE\_METHOD

The solution is to either uninstall the prelink package or add the  
following  
line to /etc/prelink.conf

-b /usr/bin/ruby

This tells prelink to not touch the ruby interpreter.

This has been killing us at work for the last couple of days. We are  
running CentOS and compiling ruby 1.9.1 from source.

Saludos,  
Doug Seifert
