Make returning "make: Nothing to be done for `all'."
-
Bradley
I'm following the screencast tutorial steps and make doesn't produce the desired results:
$ ruby extconf.rb checking for ruby.h... yes creating Makefile $ make make: Nothing to be done for `all'.
Setup:
- OS X 10.6.4
- VIM 7.2.108
- ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
-
Greg Hurrell
Did you install using the Vimball? Maybe not all of the files were correctly extracted. You could try re-extracting if that is the case.
If it did extract correctly then you should have the following in your
~/.vim/ruby/command-t
directory:Makefile controller.rb depend ext.c ext.h extconf.rb finder.rb match.c match.h match_window.rb matcher.c matcher.h prompt.rb ruby_compat.h scanner.rb settings.rb stub.rb vim/screen.rb vim/window.rb vim.rb
-
anonymous
I'm having the same problem:
- OSX 10.6.7
- ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
- MacVim 7.3 (2010 Aug 15, compiled Aug 15 2010 22:03:01)
- gcc:
Using built-in specs. Target: i686-apple-darwin10 Configured with: /var/tmp/gcc/gcc-5664~89/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5664)
Here's the list of files extracted from the vimball:
. ├── Makefile ├── controller.rb ├── extconf.rb ├── finder │ ├── buffer_finder.rb │ └── file_finder.rb ├── finder.rb ├── match_window.rb ├── prompt.rb ├── scanner │ ├── buffer_scanner.rb │ └── file_scanner.rb ├── scanner.rb ├── settings.rb └── stub.rb
Looks like I'm missing a bunch of stuff from your example. I tried downloading from both your site and Vimscripts. This is version command-t-1.1b2.vba. I also tried the previous two versions with the same result. Weird.
-
Greg Hurrell
Yes, I've seen this a few times. I think this may be a bug in the Vimball implementation itself (that it can silently fail to extract some files, despite appearing to have succeeded). Just re-extract it and the missing files should appear.
-
anonymous
I found that using an older version of Vim (7.2) and making sure to extract from same directory as the vimball did the trick. So...
$> cd ~/Downloads $> /usr/bin/vim72 command-t-1.1b2.vba
Then extract as normal using
:so %
.Happily finding files now. Thanks for the great plugin.
-
anonymous
Hi. the first few times I tried to extract the vimball. I quit out of the list of files extracted with out looking at all of them. It seems kind of silly , but when I pushed the space bar and scrolled through all the files it worked fine. Then I could make an Command-T was happy. And me too.
Thank you much for this cool program.
Reply
This topic is now closed.