segmentation fault after make in command-t

  1. anonymous

    Hi,

    I am under ubuntu 64bit, ruby 1.9.2p0, I did:

    cd ~/.vim/ruby/command-t
    ruby extconf.rb
    make
    
    houdini@moz:~/.vim/bundle/Command-T/ruby/command-t$ vim
    Vim: Caught deadly signal SEGV
    Vim: Finished.
    Segmentation fault

    Any ideas to solve this?

  2. Greg Hurrell

    Almost certainly this is due to building Command-T with a different version of Ruby than the one that Vim itself was built with and links against. By "version" I am refering not only to the version number, but also whether a 32-bit or 64-bit Ruby was used.

    Have a look at the documentation (:h command-t) for troubleshooting tips, and there are also a lot of tickets in the issue tracker which you can look at and see how other people have misbuilt the plug-in and solved it by building with a matching version of Ruby.

  3. anonymous
    $ cd ~/.vim/ruby/command-t
    $ /opt/local/bin/ruby extconf.rb
    $ make

    solved the problem

  4. anonymous

    If you use RVM, then first issue

       whereis ruby

    This will give you the version of the system ruby (say, 1.8). Then,

       rvm use 1.8.7 # or rvm install if you don't have it yet
       rake make # inside ~/.vim/bundle/command-t if you use pathogen, check the command-t readme otherwise
  5. Greg Hurrell

    With:

    $ rvm use system

    you don't even need to check which version of Ruby you should switch to; it just switches to it.

  6. Flaviu Created , edited

    I've had this problem and solved it by unsetting the GEM_PATH and GEM_HOME before running this command, by adding this to your .bashrc :

    vim() {
      (unset GEM_PATH GEM_HOME; command vim "$@")
    }

    I got this from here.

  7. anonymous

    After use @Flaviu's method, I got this:

    Vim: Caught deadly signal SEGV
  8. Greg Hurrell

    Anonymous, likely due to miscompilation (see above).

Reply

This topic is now closed.