Can't compile under Win 7 with MinGW about vimproc.vim

[Shougo]

I think gcc is not installed in your system.
You should check MinGW installation.

[Praful]

I came across this issue today. I'm using gvim 32-bit and am trying out a 64-bit version.

The mingw32.mak file has the line CC=mingw32-gcc

The mingw64.mak file has the line CC=x86_64-w64-mingw32-gcc

On the RubyInstaller site, you can download the MinGW 32-bit and 64-bit dev kits.

Whilst the 64-bit dev kit has x86_64-w64-mingw32-gcc.exe, the 32-bit one does not have mingw32-gcc.exe. Instead it has i686-w64-mingw32-gcc.exe. I don't know if newer installations of MinGW follow this naming convention.

In fact, both the 32-bit and 64-bit dev kits have a gcc.exe, which is an alias for the appropriate compiler i.e. on the 32-bit dev kit gcc.exe is the 32-bit compiler and on the 64-bit dev kit, it is the 64-bit compiler.

If you can't get vimproc to compile using MinGW, do this:

1. Download and install the 32-bit or 64-bit dev kit from the above RubyInstaller link.
2. Install vimproc (git clone etc) as mentioned on this site.
3. In a command prompt, go to the folder containing vimproc (cd [your folder]).
4. Run devkitvars.bat, which is in the dev kit folder. This will update the PATH.
5. If you're using 32-bit vim, then edit mingw32.mak in the vimproc folder and change the line beginning CC=mingw32-gcc to CC=gcc or to CC=i686-w64-mingw32-gcc
6. To compile the vimproc DLL, run make -f mingw32.mak (32-bit) or make -f mingw64.mak (64-bit).

[Shougo]

If you're using 32-bit vim, then edit mingw32.mak in the vimproc folder and change the line beginning CC=mingw32-gcc to CC=gcc or to CC=i686-w64-mingw32-gcc

You don't have to do it.

make -f mingw64.mak CC=i686-w64-mingw32-gcc

[Shougo]

#124
#123
#122

Related issues.

[Shougo]

I changed mingw32.mak uses "gcc" name by default.
If you have not "gcc" named binary, you must change $CC value.

[Praful]

Using gcc makes sense. Thanks for the tip about using the command line
CC switch.

On Wednesday, May 21, 2014, Shougo [email protected] wrote:

I changed mingw32.mak uses "gcc" name by default.
If you have not "gcc" named binary, you must change $CC value.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/86#issuecomment-43820315
.

Bye for now

Praful

[codeur4]

I try to install vimproc an on window 7
My screen on gVim when I run :VimProcInstall :

I tried to follow step by step the suggested method by Praful. It don't work and I can't figure out what is the problem. I have the followinf error :

make (e=2): the specified file is not found

Please help

[Shougo]

I think gcc is not installed.

[codeur4]

I reinstall MinGW from an other source ; I found it there
I noticed that I have now gcc file in the bin directory. So you were right.
I updated my path and run again make -f make_mingw32.mak :

...

But if I do make -f make_mingw64.mak :

I think it is ok, but if I run :VimProcInstall again in Vim I have again :

I googled 'cannot find -lmsvcrt' but found nothing
I must have a bad version of something (64 instead of 32 bit), but I can't figure out what I have to do

[Shougo]

You should read the message and the documentation....
Your installed vimproc binary is 32bit.
Because, you executed "make -f make_mingw64.mak" command.
But your Vim is 32bit. So vimproc binary is not loaded.
You must build 32bit binary.

[Shougo]

Hm. Your used MinGW is broken to build 32bit.
You should use the MinGW binary.

http://tdm-gcc.tdragon.net/download

[codeur4]

Ok thank you.
I ran the first link tdm-gcc-5.1.0-3.exe
Now, in my C:\Tools\TDM-GCC-32\bin path I have gcc (automatically put in my system path) :

I also remind that I have make (put in my user path) :

that I took from the ruby installer link proposed by Praful :

And now I have :

Is it ok or not, I don't know.
The good thing in Vim is that when I run :VimProcInstall I have no error message :

And I have no error when I run the two following commands :

But the first command with async don't show me any proposal and I don't know why.
You think it is an other problem or I have done something wrong ?

[Shougo]

You should remove the old vimproc binary.
Reinstall vimproc is recommended.

[codeur4]

I have already clean and install VimProc from Vim.
I have delete C:\Users\herve.vim\bundle\vimproc.vim\autoload\vimproc_win32.dll.
then run (same as :VimProcInstall):

Same result : no proposal with async.
Or maybe I didn't understand what you mean by 'remove the old vimproc binary'
I am confused

[codeur4]

I have suddenly a doubt. Is it the right way to install vimProc with Vundle?

Or shall I must add something like :
{'build': {'windows': 'make -f make_mingw32.mak'}} ?
Well, I tried this :

but nothing change.

[Shougo]

Hmmm..

Please test vimproc works.
:echo vimproc#system('dir')

If vimproc works, it is your async binary problem.

[codeur4]

For information I have reinstall vim64 because I run into a windows 64bit system. but the problem still remains the same.
:echo vimproc#system('dir') return

It works, so according to you it is my async binary. Do you have an idea how I can fix it?
Thanks for the time you spent with me

[Shougo]

Please upload your .vimrc file and please upload unite screenshot using <Plug>(unite_print_message) in unite buffer.

[codeur4]

Here is my vimrc at the moment.

please upload unite screenshot using (unite_print_message)

How? I looked for <Plug>(unite_print_message_log) into unite doc but I don't understand how use it?

[Shougo]

OK. I get it. You need set g:unite_source_rec_async_command.
Please read unite.vim documentation.

                    *g:unite_source_rec_async_command*
g:unite_source_rec_async_command
        Specify the filelist command and arguments in file_rec/async
        source.  It is arguments List.
>
        " Using ack-grep as recursive command.
        let g:unite_source_rec_async_command =
        \ ['ack', '-f', '--nofilter']

        " Using ag as recursive command.
        let g:unite_source_rec_async_command =
                \ ['ag', '--follow', '--nocolor', '--nogroup',
        \  '--hidden', '-g', '']
<
        The default value is ["find", "-L"] which follows symbolic
        links to have the same behaviour as file_rec, and the
        args(|g:unite_source_rec_find_args|).
        Because, "find" command is fastest.
        Note: In windows environment, you must install file list
        command and specify the variable.

[codeur4]

Awsome !
Thanks