≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #2159

Bug #2159: Error building in OSX Mavericks with either version of ruby

Kind bug
Product Command-T
When Created 2014-02-28T22:01:28Z, updated 2014-03-27T20:59:25Z
Status closed
Reporter anonymous
Tags no tags

Description

I just pulled your latest changes and tried to build command-t on my OSX mavericks (which I have been using for a while without issues) and it doesn't work. I have tried every combination of ruby version and now I don't know what to do anymore. Here are the relevant outputs:

$ mvim --version                                                                                                                                                                                                                                                                                                                                          VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 28 2014 16:30:38)
MacOS X (unix) version
Included patches: 1-52
Compiled by Homebrew
Huge version with MacVim GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_binary
+arabic          +find_in_path    -mouse_sysmouse  +tag_old_static
+autocmd         +float           +mouse_urxvt     -tag_any_white
+balloon_eval    +folding         +mouse_xterm     +tcl
+browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +fullscreen      -mzscheme        +textobjects
+cindent         -gettext         +netbeans_intg   +title
+clientserver    -hangul_input    +odbeditor       +toolbar
+clipboard       +iconv           +path_extra      +transparency
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      +python3/dyn     +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con_gui  +lua             +rightleft       +windows
+diff            +menu            +ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
+dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     +xim
+emacs_tags      +mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        -mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
+farsi           +mouse_netterm   +syntax
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX -no-cpp-precomp  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     -I/System/Library/Frameworks/Tcl.framework/Headers  -D_REENTRANT=1  -D_THREAD_SAFE=1  -D_DARWIN_C_SOURCE=1
Linking: clang   -L. -L/usr/local/lib -L. -L/usr/local/lib  -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv -framework Cocoa  -L/usr/local/lib -llua -fstack-protector -L/usr/local/lib  -L/System/Library/Perl/5.16/darwin-thread-multi-2level/CORE -lperl   -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby
$ ruby --version
ruby 2.0.0p247 (2013-06-27 revision 41674) [universal.x86_64-darwin13]

Running with ruby 2.0.0

$ ruby extconf.rb
checking for float.h... yes
checking for ruby.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for pthread.h... yes
creating Makefile

$ make
compiling ext.c
compiling match.c
compiling matcher.c
linking shared-object ext.bundle

When I run vim or mvim, I get the following when I \t :

command-t.vim could not load the C extension
Please see INSTALLATION and TROUBLE-SHOOTING in the help
For more information type:    :help command-t  

Now with 1.8:

$ /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby extconf.rb
checking for float.h... yes
checking for ruby.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for pthread.h... yes
creating Makefile

$ make
xcrun cc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I. -DHAVE_PTHREAD_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c ext.c
xcrun cc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I. -DHAVE_PTHREAD_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c match.c
xcrun cc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0 -I. -DHAVE_PTHREAD_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c matcher.c
cc -arch i386 -pipe -bundle -undefined dynamic_lookup -o ext.bundle ext.o match.o matcher.o -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch i386     -lruby  -lpthread -ldl -lobjc

Same output in vim and mvim.

Just in case this is useful information, I downloaded it using vundle and the ext.bundle lives in the ~/.vim/bundle/command-t/ruby/command-t directory.

Any help would be much appreciated

Comments

  1. Greg Hurrell 2014-03-06T14:45:17Z

    What is the output of :ruby puts RUBY_VERSION in Vim?

    On the surface, it looks like you're doing everything right. (FWIW, I'm on 10.9 as well with Homebrew-installed Vim and it works without any acrobatics, so there should be some explanation for why it's not working for you.)

  2. Carneiro 2014-03-12T14:42:26Z

    Hi Wincent, my RUBY_VERSION in Vim is: 1.8.7

    Just updated it to the latest github version and still can't get it to work. Any ideas would be much appreciated. I'd hate to have go back to ctrl-p.

  3. Carneiro 2014-03-12T14:55:11Z

    I just found out that my vim has a different ruby version to my macvim. Do you think that could be causing this issue?

    vim is running ruby 2 while macvim is running 1.8.2.

  4. Greg Hurrell 2014-03-12T15:21:15Z

    That absolutely sounds like the cause of the issue. Command-T and Vim must link against the exact same version of Ruby if you want things to work.

    If you installed Vim with Homebrew, you should install MacVim via Homebrew as well; they'll both link against Ruby 2.0.0, so you should be able to build Command-T against 2.0.0 as well and it will work in both places.

  5. Carneiro 2014-03-13T14:32:33Z

    Thank you very much.

    I reinstalled macvim with brew with the following command line:

    brew reinstall macvim --with-lua --override-system-vim --with-luajit --with-python3

    then rebuilt command-t using ruby 2, and now everything is working again, on both vim and macvim.

  6. Greg Hurrell 2014-03-27T20:59:25Z

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets