On Wed, 2015-11-25 at 10:11 +0000, Craig Small wrote: > Hmm, something isn't too happy :( > > command-t.vim could not load the C extension > > Please see INSTALLATION and TROUBLE-SHOOTING in the help > > Vim Ruby version: 2.1.5-p273 > > Expected version: 2.2.3-p173 > > For more information type: :help command-t > > Press ENTER or type command to continue > > > So.. my pbuilder has ruby 2.2.3 > but my vim is linked to libruby2.1.5 > $ ldd /usr/bin/vim | grep ruby > libruby-2.1.so.2.1 => /usr/lib/x86_64-linux-gnu/libruby- > 2.1.so.2.1 (0x00007f891aef3000) > > But, I have libruby2.2 > So, how do you tell this package to only depend on a vim that is > linked to ruby2.2 > or how do you tell command-t to link to the vim it knows about. I think this happens because you have vim 2:7.4.488-7 (from jessie) installed, which uses libruby2.1. vim in testing/unstable uses libruby2.2, so upgrading to this version would get things working. Alternatively you can remove the version requirements from the build- dependencies upon ruby and ruby-dev, and build in a pure jessie environment; the extension in general doesn't require a particular version of ruby, I just added them when I when I originally noticed that vim in testing now requires ruby 2.2. In fact, I'll probably just remove the version requirements on those build-dependencies entirely--they just get in the way when backporting the package to run on jessie. -- Sam Morris <https://robots.org.uk/> CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9
Attachment:
signature.asc
Description: This is a digitally signed message part