[vim/vim] build vim with msys2, but can't run it. (Issue #11331)

183 views
Skip to first unread message

zhucezy

unread,
Oct 10, 2022, 1:48:43 AM10/10/22
to vim/vim, Subscribed

I builded vim7.4/8.2 with msys2. But when run it in msys2 console, it will hang up(vim7.4) or prompt "not compatiable with cygwin".
I found official expaination as "you can't execute vim.exe in the MSYS2 console, open a normal Windows console for that." in installPC.txt.
But I'v got an other copy of vim.exe (version 7.4) which can be used both msys2 console and windows cmd console.
How to build an copy like that?


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331@github.com>

Christian Brabandt

unread,
Oct 10, 2022, 2:43:23 AM10/10/22
to vim/vim, Subscribed

This has been changed later than 7.4, because this causes more problem than it solves. So the correct way to use it is, for standard Windows builds, run it in a default console window. For Cygwin ones, built it it a cygwin environment. It's no longer possible to run one build in either environment


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1272847533@github.com>

K.Takata

unread,
Oct 10, 2022, 3:00:14 AM10/10/22
to vim/vim, Subscribed

If you want to build Vim that can run in the msys2 console, you should build it in a similar way as Cygwin using ./configure and make.
If you don't need to build it by yourself, you can simply use pacman -S vim to install it.

Another way to run the Win32 version of Vim in the msys2 console is enabling ConPTY by setting the MSYS environment variable to enable_pcon. (This might have some compatible issues, though.)


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1272860201@github.com>

zhucezy

unread,
Oct 10, 2022, 5:31:22 AM10/10/22
to vim/vim, Subscribed

This has been changed later than 7.4, because this causes more problem than it solves. So the correct way to use it is, for standard Windows builds, run it in a default console window. For Cygwin ones, built it it a cygwin environment. It's no longer possible to run one build in either environment

Thanks a lot. Let me try a 7.3 version.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1273037186@github.com>

zhucezy

unread,
Oct 10, 2022, 5:37:28 AM10/10/22
to vim/vim, Subscribed

If you want to build Vim that can run in the msys2 console, you should build it in a similar way as Cygwin using ./configure and make.

Thanks for your reply.
I do want compile it by myself, and i failed with Make_cygwin.mak or ./configure & make like below:
./configure --prefix=/usr
--build=i686-W64-mingw32
--with-tlib=ncurses
--without-x
--with-lua-prefix=/usr/local
--disable-gui
--disable-tclinterp
--disable-cscope
--enable-luainterp
--enable-pythoninterp=dynamic
--enable-rubyinterp=dynamic
--enable-pythoninterp=dynamic
--enable-multibyte
it still can't work in msys2 console.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1273044925@github.com>

K.Takata

unread,
Oct 10, 2022, 6:14:31 AM10/10/22
to vim/vim, Subscribed

You are using the wrong version of GCC.
If you use Start Menu, you should use the "MSYS2 MSYS" icon. Or, you can use C:\msys64\msys.exe to open the shell. Then, make sure that you are using /usr/bin/gcc (or /usr/bin/x86_64-pc-msys-gcc).

Make_cyg.mak is used for building the Win32 version of Vim on Cygwin, not for building the Cygwin version of Vim.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1273086665@github.com>

zhucezy

unread,
Oct 11, 2022, 10:38:11 PM10/11/22
to vim/vim, Subscribed

You are using the wrong version of GCC.

Understood. I should install a non-mingw version of GCC.
If I want build a version can be used in msys2, I should use the vim source get from msys2, which include patches.
Thank you very much and I'll close it.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1275506582@github.com>

zhucezy

unread,
Oct 11, 2022, 10:38:41 PM10/11/22
to vim/vim, Subscribed

Closed #11331 as completed.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/11331/issue_event/7567671744@github.com>

K.Takata

unread,
Oct 11, 2022, 10:51:59 PM10/11/22
to vim/vim, Subscribed

FYI, you can find the build script and patches for MSYS2's vim package here: https://github.com/msys2/MSYS2-packages/tree/master/vim


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1275513635@github.com>

zhucezy

unread,
Oct 13, 2022, 8:17:21 PM10/13/22
to vim/vim, Subscribed

Reopened #11331.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/11331/issue_event/7585915888@github.com>

zhucezy

unread,
Oct 13, 2022, 8:35:03 PM10/13/22
to vim/vim, Subscribed

Yes, I built vim 8.2 according to it. And I built vim 7.4 too by using it with official vim package. Thank you. @k-takata


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1278323868@github.com>

K.Takata

unread,
Oct 13, 2022, 11:57:48 PM10/13/22
to vim/vim, Subscribed

Closed #11331 as completed.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/11331/issue_event/7586752865@github.com>

K.Takata

unread,
Oct 13, 2022, 11:57:49 PM10/13/22
to vim/vim, Subscribed

Okay, closing then.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/11331/1278447425@github.com>

Reply all
Reply to author
Forward
0 new messages