You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1999: vim exits on :CommandT

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter mcj
Tags no tags

Description

I installed Command-T via vundle, however i cannot get it to work. MacVim exits when i enter :CommandT

I pulled CommandT down with:

Bundle 'git://git.wincent.dev/command-t.git'

and

:BundleInstall

I checked my mvim --version, and found +ruby and -arch x84_64, so i attempted to make the plugin as follows: 

$ cd ~/.vim/bundle/command-t/ruby/command-t
$ rvm use system
$ ruby extconf.rb
$ export ARCHFLAGS="-arch x86_64"
$ make
$ sudo make install

make gave the following output -- i don't know enough to be sure what's going wrong here, but it seems _wrong_ 

cc -arch i386 -arch x86_64 -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 -arch x86_64     -lruby  -lpthread -ldl -lobjc  
ld: warning: ignoring file ext.o, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 1 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): ext.old: warning: 
ignoring file match.o, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 1 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): match.o
ld: warning: ignoring file matcher.o, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 1 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): matcher.o

sudo make install - returned

/usr/bin/install -c -m 0755 ext.bundle /Library/Ruby/Site/1.8/universal-darwin11.0

now when i open MacVim and issue :CommandT it exits with the following output: 

dyld: lazy symbol binding failed: Symbol not found: _rb_intern2
  Referenced from: /Users/mcooganj/.vim/bundle/Command-T/ruby/command-t/ext.bundle
  Expected in: flat namespace

dyld: Symbol not found: _rb_intern2
  Referenced from: /Users/mcooganj/.vim/bundle/Command-T/ruby/command-t/ext.bundle
  Expected in: flat namespace

Vim: Caught deadly signal TRAP
Vim: Finished.

Comments

  1. Greg Hurrell

    Two questions:

    1. What version of MacVim are you using? (Is it a downloaded snapshot or something you built yourself?)
    2. Why did you do the ARCHFLAGS export?
  2. mcj Created , edited

    Hi,

    I brewed MacVim with

    $ brew install macvim

    and i did the ARCHFLAGS export, as i read the following in the README.txt

    First you have to check the platfom Vim was built for: 

    vim --version
 ...
 Compilation: gcc ... -arch i386 ...
 ...

    and make sure you use the correct ARCHFLAGS during compilation: 

    export ARCHFLAGS="-arch i386"
make
  3. Greg Hurrell

    Closing due to lack of activity. Enough time has passed since this original report that all the version numbers (etc) will have changed, so feel free to open another issue if you run into any problem like this again.

  4. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
  5. acandael

    I encounter exactly the same problem, I changed the env variable to 

    export ARCHFLAGS="-arch x86_64"

    but now, when I type

    :CommandT

    in MacVim

    it crashes with the following error:

    acandael: /Users/acandael/.vim/bundle/command-t/ruby/command-t
$dyld: lazy symbol binding failed: Symbol not found: _rb_intern2
  Referenced from: /Users/acandael/.vim/bundle/command-t/ruby/command-t/ext.bundle
  Expected in: flat namespace

dyld: Symbol not found: _rb_intern2
  Referenced from: /Users/acandael/.vim/bundle/command-t/ruby/command-t/ext.bundle
  Expected in: flat namespace

Vim: Caught deadly signal TRAP
Vim: Finished.

    How can I fix this?

    thanks for your help,

    Anthony

  6. Greg Hurrell

    I'm going to suggest we continue the discussion on ticket #2182 which you just created.

Add a comment

Comments are now closed for this issue.

Menu