Re: Patch 8.2.1691

I'm building vim on Windows 7 using MinGW-W64, gcc 8.1.0. On building the latest pull, I get: [...] In file included from main.c:11: globals.h:394:50: error: 'TTFLAG_STATIC' undeclared here (not in a function); did you mean 'VAR_STATIC'? EXTERN type_T t_unknown INIT6(VAR_UNKNOWN, 0, 0,

Re: Patch 8.2.0775

By building on Windows 7 with Mingw-w64 I'm getting: [...] obji686/if_lua.o:if_lua.c:(.text+0x4096): undefined reference to `luaL_loadstring' collect2.exe: error: ld returned 1 exit status make: *** [gvim.exe] Error 1 Error by compiling gvim.exe -- Cesar -- -- You received this message from

Dead keys don't work on a terminal window in gvim

I'm using gvim 8.1.1148 on Windows 7 with US-International layout keyboard. Normally, when I use the command prompt, cmd.exe, with code page 1252, and press the ' key (dead key) and the "a" key I get "á", but on a terminal window in gvim I get "'a". The same happens with the keys "^" and "a". I

Re: Patch 8.1.0942

By building vim on Windows 7 with MinGW-W64, ruby 2.3.1p112, I get: [...] if_ruby.c:68:11: fatal error: dlfcn.h: No such file or directory # include ^ compilation terminated. make: *** [gobjZi686/if_ruby.o] Error 1 Error by compiling gvim.exe

Re: Patch 8.1.0881

By compiling vim on Windows 7 with MinGW-W64, I'm getting: [...] ex_docmd.c: In function 'do_one_cmd': ex_docmd.c:2015:36: error: 'RESTRICT' undeclared (first use in this function); did you mean 'RE_STRICT'? if (restricted != 0 && (ea.argt & RESTRICT))

Re: Patch 8.1.0474

On 14/10/2018 02:48 p.m., Bram Moolenaar wrote: > > Cesar Romani wrote: >> >> Compiling on Windows 7 with MinGW, I get: >> >> >> [...] >> gcc -c -Iproto -DWIN32 [...] auto/if_perl.c -o gobjZi686/if_perl.o >> if_perl.xs:38:1

Re: Patch 8.1.0474

On 14/10/2018 09:25 a.m., Bram Moolenaar wrote: > > Patch 8.1.0474 > Problem:Directory where if_perl.c is written is inconsistent. > Solution: use auto/if_perl.c for MS-Windows. (Ken Takata, closes #3540) > Files: src/Make_bc5.mak, src/Make_cyg_ming.mak, src/Make_mvc.mak Compiling

Re: [vim/vim] "vim -?" shows incorrect encoding in cmd.exe (#3311)

On 09/10/2018 03:31 p.m., scootergrisen (Vim Github Repository) wrote: > If i run stuff like cmd.exe /h or audacity.exe /h the text shows with > correct encoding so i think the problem is with Vim. Change the code page to 1252, and try it again. -- -- You received this message from the

Re: Error when trying to compile vim with statically linked python

On 01/07/2018 08:48 p.m., Ken Takata wrote: > Hi Cesar, > > 2018/7/2 Mon 8:59:44 UTC+9 Cesar wrote: >> When trying to compile vim 8.1.137 with statically linked pyhon 2.7.14, >> using MinGW-W64 on Windows 7, I get: >> >> >> [...] >> gcc -Iproto -DWIN32 -DWINVER=0x0600

Error when trying to compile vim with statically linked python

When trying to compile vim 8.1.137 with statically linked pyhon 2.7.14, using MinGW-W64 on Windows 7, I get: [...] gcc -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 [...] -Lc:/python27/libs -lpython27 gobjZi686/ex_cmds2.o:ex_cmds2.c:(.text+0x761a): undefined

Re: Patch 8.0.1824

I'm compiling vim on Windows 7 with MinGW-W64, gcc 7.2.0. I get some warnings: gcc -c -Iproto -DWIN32 [...] -o gobjZi686/terminal.o terminal.c: In function 'term_and_job_init': terminal.c:5504:30: warning: passing argument 2 of 'build_argv_from_string' from incompatible

Re: Please change the default for 'wildmode'

On 09/05/2018 05:44 a.m., Christian Brabandt wrote: > > On Mi, 09 Mai 2018, Tony Mechelynck wrote: > >> With my longest:full,full setting I don't have to delete anything, I >> just repeatedly hit the right-arrow key (or down-arrow to descend into >> directories); if there are too many matches I

Re: Patch 8.0.1742

On 21/04/2018 12:49 p.m., Bram Moolenaar wrote: > > Patch 8.0.1742 > Problem:Cannot get a list of all the jobs. Cannot get the command > of the job. > Solution: When job_info() is called without an argument return a > list of jobs. Otherwise, include the command

Re: Patch 8.0.1723

On 16/04/2018 08:16 a.m., Bram Moolenaar wrote: > > [...] > If you notice a problem because of this patch, please speak up! > Also if it's just a compiler warning. We want to know if this C99 > feature works for everybody. I'm using mingw-w64 on Windows 7, gcc 7.2.0, and I don't get any

Re: Patch 8.0.1174

On 04/10/2017 11:05 a.m., Bram Moolenaar wrote: > > Patch 8.0.1174 > Problem:Mac Terminal.app has wrong color for white. > Solution: Use white from the color cube. > Files: src/globals.h, src/term.c, src/syntax.c > > > *** ../vim-8.0.1173/src/globals.h 2017-09-16 20:54:47.082560506

Re: No rule to make terminal.c

On 19/09/2017 06:56 p.m., M Kelly wrote: > I think terminal.c was deleted in the latest version ?? > I get the same error compiling on Windows with MinGW. -- Cesar -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to.

Re: [vim/vim] needless key after :terminal on Windows GUI (#1924)

On 03/08/2017 01:45 p.m., Bram Moolenaar (Vim Github Repository) wrote: > Closed #1924 via e9c21ae > . > But, what is the solution? I'm also having the same problem with the

Re: Patch 8.0.0187

On 14/01/2017 02:12 p.m., Bram Moolenaar wrote: > > Patch 8.0.0187 > Problem:Building with a new Ruby version fails. > Solution: Use ruby_sysinit() instead of NtInitialize(). (Tomas Volf, > closes #1382) > Files: src/if_ruby.c > > > *** ../vim-8.0.0186/src/if_ruby.c

Re: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

On 08/11/2016 04:08 a.m., mattn wrote: > Hi, Dr. Chip and list. > > I met some problems on netrw on Windows for a long time. Most of > operations which use Windows commands of cmd.exe doesn't work because > netrw checks the command exists by executable(). The commands are > defined like: > > let

Re: gx doesn't work anymore with vim 8.0.4

On 15/09/2016 02:22 p.m., Cesar Romani wrote: > On 15/09/2016 08:06 a.m., Charles E Campbell wrote: > > Cesar Romani wrote: > >> I'm using vim 8.0.4 on Windows 7 compiled with MinGW. > >> When doing gx on an url I get: > >> > >> E117: Unknown func

Re: gx doesn't work anymore with vim 8.0.4

On 15/09/2016 08:06 a.m., Charles E Campbell wrote: > Cesar Romani wrote: >> I'm using vim 8.0.4 on Windows 7 compiled with MinGW. >> When doing gx on an url I get: >> >> E117: Unknown function: netrw#CheckIfRemote >> E116: Invalid arguments for function netrw#Bro

gx doesn't work anymore with vim 8.0.4

I'm using vim 8.0.4 on Windows 7 compiled with MinGW. When doing gx on an url I get: E117: Unknown function: netrw#CheckIfRemote E116: Invalid arguments for function netrw#BrowseX Many thanks in advance, -- Cesar -- -- You received this message from the "vim_dev" maillist. Do not top-post!

Re: Patch 7.4.2057

I'm building vim on Windows 7 with MinGW. On latest pull, I'm getting a lot of undefined references. Attached is the output. Many thanks in advance, -- Cesar -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For

Warnings in ex_cmds2.c, getchar.c, pathdef.c, undo.c, os_win32.c

By building vim 7.4.1385 on Windows 7 with MinGW, I get following warnings: [...] ex_cmds2.c: In function 'source_pack_plugin': ex_cmds2.c:3076:9: warning: 'p6' may be used uninitialized in this function [-Wmaybe-uninitialized] c = *p6; ^ [...] getchar.c: In

Warnings in pathdef.c and if_mzsch.c

By compiling vim on Windows 7 with MinGW I get the following warnings: [...] pathdef.c:6:32: warning: unknown escape sequence: '\l' [enabled by default] [...] if_mzsch.c: In function 'startup_mzscheme': if_mzsch.c:1104:2: warning: pointer targets in passing argument 1 of

Re: [vim] Compile Vim 7.4.1342 Error (#641)

It has no effect. Even with the above patch I get the same error: objZi386/eval.o:eval.c:(.text+0x356b): undefined reference to `get_job_options' collect2.exe: error: ld returned 1 exit status make: *** [vim.exe] Error 1 Error by compiling vim.exe

Re: Error on building vim.exe with latest pull

On 16/02/2016 10:48 a.m., Cesar Romani wrote: > On 16/02/2016 10:10 a.m., mattn wrote: > > https://gist.github.com/8b6c478ca91e985452b8 > > > > This will fix your problem maybe. > > Yes, it does it. Thanks, > > Regards, > It com

Re: Error on building vim.exe with latest pull

On 16/02/2016 10:10 a.m., mattn wrote: > https://gist.github.com/8b6c478ca91e985452b8 > > This will fix your problem maybe. Yes, it does it. Thanks, Regards, -- Cesar -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying

Re: Patch 7.4.1143

I'm getting: [...] ex_cmds.c:560:48: error: 'DBL_MAX' undeclared (first use in this function) nrs[lnum - eap->line1].st_u.value_flt = -DBL_MAX; ^ ex_cmds.c:560:48: note: each undeclared identifier is reported only once

Re: Patch 7.4.1065

Thanks, now it works. Regards, -- Cesar -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to

Re: Patch 7.4.1065

On 09/01/2016 08:58 a.m., Bram Moolenaar wrote: > > Patch 7.4.1065 > Problem:Cannot use the "dll" options on MS-Windows. > Solution: Support the options on all platforms. Use the built-in name as > the default, so that it's clear what Vim is looking for. > Files:

Re: Patch 7.4.907

On 02/11/2015 09:30 a.m., Bram Moolenaar wrote: > > Patch 7.4.907 > Problem:Libraries for dynamically loading interfaces can only be > defined > at compile time. > Solution: Add options to specify the dll names. (Kazuki Sakamoto, > closes #452) > Files:

Re: Patch 7.4.759

On 26/06/2015 01:17 p.m., Christian Brabandt wrote: Hi Cesar! On Fr, 26 Jun 2015, Cesar Romani wrote: On 25/06/2015 11:28 a.m., Bram Moolenaar wrote: Patch 7.4.759 Problem:Building with Lua 5.3 doesn't work, symbols have changed. Solution: Use the new names for the new version

Re: Patch 7.4.759

On 25/06/2015 11:28 a.m., Bram Moolenaar wrote: Patch 7.4.759 Problem:Building with Lua 5.3 doesn't work, symbols have changed. Solution: Use the new names for the new version. (Felix Schnizlein) Files: src/if_lua.c When building on Windows with MinGW32 and Lua 5.1.4, I get:

Re: Patch 7.4.726

On 05/05/2015 09:55 p.m., Christian J. Robinson wrote: On Tue, 5 May 2015, Andrei Olsen wrote: On Tuesday, May 5, 2015 at 5:00:10 PM UTC+2, Cesar wrote: By compiling on Windows 7 with mingw32 I still get: [...] make: *** [GvimExt/gvimext.dll] Error 2 Error by compiling gvim.exe Had a

Re: Patch 7.4.726

By compiling on Windows 7 with mingw32 I still get: [...] make -C GvimExt -f Make_ming.mak CROSS=no CROSS_COMPILE= make[1]: Entering directory `/home/caesar/vim/src/GvimExt' g++ -O2 -DFEAT_GETTEXT -c gvimext.cpp -o gvimext.o windres --preprocessor=g++ -E -xc -DRC_INVOKED --input-format=rc

Re: Patch 7.4.689

On 03/04/2015 11:00 a.m., Cesar Romani wrote: On 03/04/2015 10:34 a.m., Bram Moolenaar wrote: Cesar Romani wrote: On 03/04/2015 07:58 a.m., Bram Moolenaar wrote: Patch 7.4.689 Problem: On MS-Windows, when 'autochdir' is set, diff mode with files in different

Re: Patch 7.4.689

On 03/04/2015 10:34 a.m., Bram Moolenaar wrote: Cesar Romani wrote: On 03/04/2015 07:58 a.m., Bram Moolenaar wrote: Patch 7.4.689 Problem:On MS-Windows, when 'autochdir' is set, diff mode with files in different directories does not work. (Axel Bender) Solution

Re: Patch 7.4.689

On 03/04/2015 07:58 a.m., Bram Moolenaar wrote: Patch 7.4.689 Problem:On MS-Windows, when 'autochdir' is set, diff mode with files in different directories does not work. (Axel Bender) Solution: Remember the current directory and use it where needed. (Christian Brabandt) Files:

Re: problems with compiling vim with DIRECTX=yes on Windows

On 16/01/2015 10:19 p.m., Ken Takata wrote: Hi Cesar, 2015/1/16 Fri 23:56:08 UTC+9 Cesar wrote: By compiling vim with DIRECTX=yes on Windows 7 with MinGW I get: -- [...] gcc -c -Iproto -DWIN32 ... gui_dwrite.cpp -o gobjZi386/gui_dwrite.o gui_dwrite.cpp:21:20: fatal error:

problems with compiling vim with DIRECTX=yes on Windows

By compiling vim with DIRECTX=yes on Windows 7 with MinGW I get: -- [...] gcc -c -Iproto -DWIN32 ... -DFEAT_DIRECTX -DDYNAMIC_DIRECTX -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i386 -Wall -IC:/perl/lib/Core -DFEAT_PERL

Re: Patch 7.4.570

On 14/01/2015 05:52 p.m., Ken Takata wrote: Hi Cesar, 2015/1/15 Thu 0:40:05 UTC+9 Cesar wrote: [...] gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb6c): undefined reference to `rb_gc_writebarrier_unprotect_promoted' gobjZi386/if_ruby.o:if_ruby.c:(.text+0xb7c): undefined reference to

Re: Patch 7.4.570

On 14/01/2015 08:04 a.m., Bram Moolenaar wrote: Patch 7.4.570 Problem:Building with dynamic library does not work for Ruby 2.2.0 Solution: Change #ifdefs and #defines. (Ken Takata) Files: src/if_ruby.c *** ../vim-7.4.569/src/if_ruby.c 2014-11-27 17:44:05.376820913 +0100

Re: [count]tabfind doesn't work properly

On 28/04/2014 04:19 p.m., Christian Brabandt wrote: Hi Cesar! On Do, 24 Apr 2014, Cesar Romani wrote: I'm using vim 7.3.264 on Windows 7. '[count]find file' works fine. If I do, for example ':2find file' it finds the correct version of file, and if I do ':3find file' it outputs

Re: [count]tabfind doesn't work properly

On 24/04/2014 10:46 a.m., Ben Fritz wrote: On Thursday, April 24, 2014 10:23:51 AM UTC-5, Cesar wrote: I'm using vim 7.3.264 on Windows 7. ... If I do for example ':14tabf file' it always finds the first version... It used to work with older vim versions. Did you actually mean 7.4.264

[count]tabfind doesn't work properly

I'm using vim 7.3.264 on Windows 7. '[count]find file' works fine. If I do, for example ':2find file' it finds the correct version of file, and if I do ':3find file' it outputs the message 'E347: No more file file found in path' what it is correct and expected, but with '[count]tabfind' it

Re: Spelling support doesn’t deal with ‘’’ correctly

On 08/03/2011 03:01 p.m., Dominique Pellé wrote: [...] I found the following patch which adds support of Hunspell dictionary in Vim: https://bugzilla.redhat.com/show_bug.cgi?id=219777 I tried the patch and it still works with latest vim-7.3.138 (I did not test it extensively yet). With

Re: ActivePerl 5.18.1 fails to compile

On 07/12/2013 11:07 a.m., Cesar Romani wrote: On 07/12/2013 08:29 a.m., Bram Moolenaar wrote: Cesar Romani wrote: [...] How about with this one: --- Make_ming.mak.org 2013-11-22 00:16:21 -0500 +++ Make_ming.mak 2013-12-06 21:21:05 -0500

Re: ActivePerl 5.18.1 fails to compile

On 06/12/2013 03:03 p.m., Bram Moolenaar wrote: Cesar Romani wrote: [...] ifeq (yes, $(DYNAMIC_PERL)) DEFINES += -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl$(PERL_VER).dll\ +EXTRA_LIBS += -L$(PERL)/lib/CORE -lperl$(PERL_VER) else EXTRA_LIBS += $(PERL)/lib/CORE/perl$(PERL_VER).lib

Re: ActivePerl 5.18.1 fails to compile

On 05/12/2013 09:21 a.m., Ken Takata wrote: Hi, 2013/12/5 Thu 10:50:55 UTC+9 Cesar wrote: The only command I've used with the above patched makefile, was: make -f Make_cyg.mak but I used StrawberryPerl-5.18.1.1-32bit and ActivePerl-5.18.1.1-32bit, built on Windows 7 Home Premium 64-bit using

Re: ActivePerl 5.18.1 fails to compile

On 04/12/2013 07:35 p.m., Steve Hall wrote: On Wed, Dec 4, 2013 at 6:03 PM, Cesar Romanicesar.rom...@gmail.com wrote: On 04/12/2013 08:09 a.m., Bram Moolenaar wrote: Is this specific for this version of Perl? If so, what kind of condition (flag) should we use for this? Cygwin -- Both

Re: ActivePerl 5.18.1 fails to compile

On 01/12/2013 09:11 a.m., Steve Hall wrote: FINALLY! Thanks Ken and Cesar for the help. Okay, it took three parts to get my Cygwin cross-compile for Windows build to work with Perl: 1. Patching vim\Make_cyg.mak (via Cesar Romani) --- C:\vim\Make_cyg.mak +++ C:\vim\Make_cyg.mak @@ -155,6

Re: ActivePerl 5.18.1 fails to compile

On 30/11/2013 08:09 a.m., Steve Hall wrote: [...] With the revised if_perl.xs from your previous link, I still get the following build errors in a Cygwin build. 1:In file included from /cygdrive/c/strawberry/perl/lib/CORE/sys/socket.h:30:0, 2: from

Re: ActivePerl 5.18.1 fails to compile

On 28/11/2013 01:18 a.m., Konovalov, Vadim wrote: From: vim_dev@googlegroups.com On Behalf Of tux. Konovalov, Vadim schrob am Mittwoch, 27. November 2013 um 06:46 Zeit: I can investigate later today, if you wish. I'd like you to. :) ActivePerl 5.18.1 binaries are built with VC6 compiler,

Re: ActivePerl 5.18.1 fails to compile

On 28/11/2013 05:10 p.m., Cesar Romani wrote: On 28/11/2013 01:18 a.m., Konovalov, Vadim wrote: From: vim_dev@googlegroups.com On Behalf Of tux. Konovalov, Vadim schrob am Mittwoch, 27. November 2013 um 06:46 Zeit: I can investigate later today, if you wish. I'd like you

indent for cmake doesn't work well

Suppose I have the following text inside CMakeLists.txt (i.e. set ft=cmake): CursesDialog/cmCursesBoolWidget CursesDialog/cmCursesCacheEntryComposite CursesDialog/cmCursesDummyWidget Notice that the lines are indented at least 4 spaces. If I yank the text

Re: problem with spellsuggest on vim 7.4.5

On 22/08/2013 07:14 a.m., Bram Moolenaar wrote: Cesar Romani wrote: spellsuggest with 'set sps:file:{filename}' doesn't work. I'm using vim 7.4.5 on windows 7. I created a file, say sps.txt, and put there the following lines: Enantes/Antes chaofa/chaufa aser/hacer kion/kión sutra

problem with spellsuggest on vim 7.4.5

spellsuggest with 'set sps:file:{filename}' doesn't work. I'm using vim 7.4.5 on windows 7. I created a file, say sps.txt, and put there the following lines: Enantes/Antes chaofa/chaufa aser/hacer kion/kión sutra/sūtra Suppose I have a file, say test.txt, with the following line: Enantes pude

default value of variable VIM changed?

Was it changed the default value for the variable VIM? I used to have VIM=C:\Vim and by updating from 7.4a.35 to 7.4a.39 I get VIM=C:\Vim\vim73 Many thanks in advance, -- Cesar -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

Re: default value of variable VIM changed?

On 22/07/2013 10:51 a.m., Bram Moolenaar wrote: Cesar Romani wrote: Was it changed the default value for the variable VIM? I used to have VIM=C:\Vim and by updating from 7.4a.35 to 7.4a.39 I get VIM=C:\Vim\vim73 Many thanks in advance, I don't think anything changed. Vim tries

Re: bug with 7.3.981

On 21/05/2013 05:04 a.m., Bram Moolenaar wrote: Cesar Romani wrote: By updating from 7.3.969 to 7.3.981 the following command doesn't work anymore: %s//\=''.matchstr(getline(.), '\d\+\ze').'' Let's say I use this command on the following text: Title Action=GoTo Page=Table of Contents 5

Re: Patch 7.3.1005

On 22/05/2013 08:17 p.m., h_east wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well. It appears to have solved for me. Best regards, Hirohito Higashi It doesn't work. It only works

Re: Patch 7.3.1005

On 23/05/2013 11:32 a.m., Bram Moolenaar wrote: Cesar Romani wrote: On 22/05/2013 08:17 p.m., h_east wrote: Hi, Cesar 2013/5/23(Thu) 8:04:11 UTC+9 Cesar: It doesn't solve the issue for %s/^\n\+/\r. It gets stuck as before. Really? My vim7.3.1005 works well

vim 7.3.1004 hangs indefinitely with some commands

By using vim 7.3.1004 on Windows 7, the following command doesn't work anymore: %s/^\n\+/\r it hangs indefinitely, say, with the following text (without dashes): Tread lightly, she is near Under the snow, Speak gently, she can hear The daisies grow.

Re: Patch 7.3.1005

On 22/05/2013 04:02 p.m., Bram Moolenaar wrote: Patch 7.3.1005 Problem:Get stuck on regexp \n* and on %s/^\n\+/\r. Solution: Fix handling of matching a line break. (idea by Hirohito Higashi) Files: src/regexp_nfa.c *** ../vim-7.3.1004/src/regexp_nfa.c 2013-05-21

bug with 7.3.981

By updating from 7.3.969 to 7.3.981 the following command doesn't work anymore: %s//\=''.matchstr(getline(.), '\d\+\ze').'' Let's say I use this command on the following text: Title Action=GoTo Page=Table of Contents 5/Title Title Action=GoTo Page=Acknowledgements 7/Title Title Action=GoTo

Re: Can't build with racket 4.2 using MinGW anymore

On 18/02/2013 10:41 a.m., Sergey Khorev wrote: but vim with racket 4.2.3 doesn't compile with DYNAMIC_MZSCHEME=yes anymore. As I wrote previously, if you want DYNAMIC_MZSCHEME, you need to either use version 3.x or build Racket yourself with conservative GC. I know that, but before

Re: Valgrind errors when compiled with MzScheme

On 18/02/2013 10:38 a.m., Sergey Khorev wrote: The problem above only occurs at runtime using racket 5.3.2 with the same command line. With racket 5.3.3 it works fine. Works fine for me. Did you delete mzscheme_base.c and *.o files before building Vim with another version of

Re: Can't build with Perl using Make_ming.mak any more [semi-solved]

On 21/02/2013 07:55 a.m., Ken Takata wrote: Hi Christian, 2013/02/21 Thu 7:50:35 UTC+9 Heptite wrote: I used to build using Make_cyg.mak but stopped in recent months because it no longer worked for me when including one of the scripting interpreters. I include Perl, Python and Ruby, but I

Re: Can't build with racket 4.2 using MinGW anymore

On 17/02/2013 01:06 a.m., Sergey Khorev wrote: I'm using MinGW with gcc-4.6.2, Racket 4.2.5 and MZSCHEME=c:/plt MZSCHEME_VER=3m_6ncd1k DYNAMIC_MZSCHEME=yes MZSCHEME_GENERATE_BASE=yes and the command line is: make -f Make_ming.mak Ok, I encounterred

Re: Valgrind errors when compiled with MzScheme

On 17/02/2013 01:18 a.m., Sergey Khorev wrote: I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using MinGW on Windows 7, 64-bit and whenever I run, say ':mzscheme 5' a windows pops up with the message: Your command line to build? Works fine with Racket 5.3.3

Re: Valgrind errors when compiled with MzScheme

I built vim with racket 5.3.2 (with racket 4.2.5 is not possible) using MinGW on Windows 7, 64-bit and whenever I run, say ':mzscheme 5' a windows pops up with the message: ViImproved - A Text Editor has stopped working A problem caused the program to stop working

Re: Can't build with racket 4.2 using MinGW anymore

If I compile vim with MSVC, Racket 4.2.5 and MZSCHEME=c:\plt MZSCHEME_VER=3m_6ncd1k DYNAMIC_MZSCHEME=yes and with the command line: nmake -f Make_mvc.mak I get: Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. Tcl

Re: Can't build with racket 4.2 using MinGW anymore

On 08/02/2013 10:41 p.m., Sergey Khorev wrote: On Sat, Feb 9, 2013 at 12:36 AM, Cesar Romani cesar.rom...@gmail.com mailto:cesar.rom...@gmail.com wrote: I'm building vim on Windows 7 with MinGW. It cannot be compiled with racket 4.2 anymore. Racket 4.2.3 works fine for me

Re: Can't build with racket 4.2 using MinGW anymore

On 08/02/2013 10:41 p.m., Sergey Khorev wrote: On Sat, Feb 9, 2013 at 12:36 AM, Cesar Romani cesar.rom...@gmail.com mailto:cesar.rom...@gmail.com wrote: I'm building vim on Windows 7 with MinGW. It cannot be compiled with racket 4.2 anymore. Racket 4.2.3 works fine for me

Re: compiling failed for vim7.3.531 with latest Racket 5.2 on Windows 7 using MinGW

If I use MSVC with MZSCHEME=c:\plt MZSCHEME_VER=3m_6ncd1k DYNAMIC_MZSCHEME=yes and the command line: nmake -f Make_mvc.mak I get: Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. Tcl requested (version 85) - root dir is

Can't build with racket 4.2 using MinGW anymore

I'm building vim on Windows 7 with MinGW. It cannot be compiled with racket 4.2 anymore. It used to get compiled before patch 7.3.791 Now I always get: [...] if_mzsch.c: In function 'window_new': if_mzsch.c:1782:21: error: lvalue required as left operand of assignment if_mzsch.c: In function

Re: Patch 7.3.798

On 31/01/2013 10:36 p.m., Sergey Khorev wrote: It also doesn't work on Windows by building with MinGW. I always get: [...] ... -freg-struct-return -s -DINCLUDE_MZSCHEME_BASE if_mzsch.c -o gobjZi386/if_mzsch.o if_mzsch.c: In function 'window_new':

Re: Patch 7.3.798

It also doesn't work on Windows by building with MinGW. I always get: [...] ... -freg-struct-return -s -DINCLUDE_MZSCHEME_BASE if_mzsch.c -o gobjZi386/if_mzsch.o if_mzsch.c: In function 'window_new': if_mzsch.c:1747:21: error: lvalue required as left operand of assignment if_mzsch.c: In

Re: Patch 7.3.791

I'm building vim on windows 7 with MinGW. After that patch I get the following error: [...] ... -freg-struct-return -s -DINCLUDE_MZSCHEME_BASE if_mzsch.c -o gobjZi386/if_mzsch.o if_mzsch.c: In function 'window_new': if_mzsch.c:1747:21: error: lvalue required as left operand of assignment

Re: Patch 7.3.773

On 19/01/2013 08:02 a.m., Bram Moolenaar wrote: Patch 7.3.773 (after 7.3.767) Problem:Crash when OriginalFirstThunk is zero. Solution: Skip items with OriginalFirstThunk not set. (Ken Takata) Files: src/mbyte.c *** ../vim-7.3.772/src/mbyte.c 2013-01-17 14:39:43.0

Re: Patch 7.3.773

On 19/01/2013 01:13 p.m., Bram Moolenaar wrote: Casar Romani wrote: I'm building vim on windows 7 with MinGW. By updating to the latest release I got the following error by make: [...] In file included from if_perl.xs:16:0: vim.h:2188:21: fatal error: EXTERN.h: No

Re: Patch 7.3.773

On 19/01/2013 01:13 p.m., Bram Moolenaar wrote: Casar Romani wrote: I'm building vim on windows 7 with MinGW. By updating to the latest release I got the following error by make: [...] In file included from if_perl.xs:16:0: vim.h:2188:21: fatal error: EXTERN.h: No

error buy building on the latest update

I'm building vim on windows 7 with MinGW. The latest built was 766. By updating to the latest release I got the following error: [...] In file included from if_perl.xs:16:0: vim.h:2188:21: fatal error: EXTERN.h: No such file or directory compilation terminated. make: ***

Re: Compiling vim with latest Racket fails

On 04/12/2012 10:24 p.m., Sergey Khorev wrote: if_mzsch.c:848:4: error: #error Precise GC v.4+ or Racket with futures/places do not support dynamic MzScheme Default Racket garbage collector (3m) doesn't support dynamic loading of dlls. For your reference this is how I build Vim with the

Re: Compiling vim with latest Racket fails

On 02/12/2012 07:25 a.m., Sergey Khorev wrote: I'm building vim 7.3.744 on Windows 7 with MinGW. By compiling it with Racket 5.3.1 I get: My comment about Make_cyg applies to Make_ming as well. You need to patch a Racket header file and use my patch for Vim. After applying your patch and

Compiling vim with latest Racket fails

I'm building vim 7.3.744 on Windows 7 with MinGW. By compiling it with Racket 5.3.1 I get: In file included from if_mzsch.h:15:0, from os_win32.c:26: c:/Racket/include/scheme.h:890:3: error: unknown type name 'uintptr_t' In file included from

compile error by updating from 7.3.718 to 7.3.728

I'm building vim on windows 7 with mingw. By updating it from 7.3.718 to 7.3.728 I got: [...] if_ruby.c:339:21: error: static declaration of 'rb_num2long_stub' follows non-static declaration c:/ruby193/include/ruby-1.9.1/ruby/ruby.h:502:14: note: previous declaration of

Re: Patch 7.3.725

I'm building vim on windows 7 with mingw. By updating it from 7.3.718 to 7.3.725 I get: [...] if_ruby.c:339:21: error: static declaration of 'rb_num2long_stub' follows non-static declaration c:/ruby193/include/ruby-1.9.1/ruby/ruby.h:502:14: note: previous declaration of

Problem by updating from 692 to 709

I'm building vim on windows 7. By updating from 692 to 709 I got the following problem: If I open 'gvim -N -u NONE file' and I type something, say foo, and if I want to change a character, say f, to n using r in normal mode, it doesn't work. I always get the same character. Many thanks in

Re: Patch 7.3.582

I'm building vim on windows 7 with MinGW. By upgrading from 7.3.566 to 7.3.582 I get the following compile error: --- ... os_win32.c: In function 'mch_avail_mem': os_win32.c:5012:2: error: unknown type name 'MEMORYSTATUSEX' os_win32.c:5014:4: error: request for member 'dwLength'

compiling failed for vim7.3.531 with latest Racket 5.2 on Windows 7 using MinGW

By compiling vim 7.3.531 with the the latest Racket 5.2 on Windows 7 using MinGW, I get: if_mzsch.c:806:4: error: #error Precise GC v.4+ or Racket with futures/places do not support dynamic MzScheme make: *** [gobjZ/if_mzsch.o] Error 1 The only

Re: compiling failed for vim7.3.531 with latest Racket 5.2 on Windows 7 using MinGW

On 29/05/2012 11:25 a.m., Sergey Khorev wrote: if_mzsch.c:806:4: error: #error Precise GC v.4+ or Racket with futures/places do not support dynamic MzScheme make: *** [gobjZ/if_mzsch.o] Error 1 The only changes I did on Make_ming.mak are:

Re: Patch 7.3.189

On 10/05/2011 10:29 a.m., Bram Moolenaar wrote: Patch 7.3.189 (after 7.3.186) Problem:Can't build without +clipboard feature. (Christian Ebert) Solution: Add the missing #ifdef. Files: src/normal.c *** ../vim-7.3.188/src/normal.c2011-05-10 16:12:40.0 +0200 ---

Re: Patch 7.3.189

On 11/05/2011 01:52 p.m., Bram Moolenaar wrote: Cesar Romani wrote: On 10/05/2011 10:29 a.m., Bram Moolenaar wrote: Patch 7.3.189 (after 7.3.186) Problem:Can't build without +clipboard feature. (Christian Ebert) Solution: Add the missing #ifdef. Files: src

Re: Patch 7.3.083

By building vim 7.3.083 on Win XP with MinGW, I'm getting: ... gcc -c -Iproto -DWIN32 ... fileio.c -o gobjZ/fileio.o fileio.c:10306:1: error: expected declaration specifiers or '...' before '(' token fileio.c:10306:1: error: expected declaration specifiers or '...' before

Re: Patch 7.3.008

I'm using vim 7.3.6, built on Win XP with MinGW. By updating to 7.3.11 It builds fine to gvim.exe but building to vim.exe 7.3.11 gives: ... gcc -c ... tag.c -o objZ/tag.o tag.c: In function 'do_tag': tag.c:128:1: internal compiler error: Segmentation fault make: ***

Re: Patch 7.3.008

On 23/09/2010 09:49 a.m., Onur Küçük wrote: On Thu, 23 Sep 2010 08:18:23 -0500 Cesar Romanicesar.rom...@gmail.com wrote: I'm using vim 7.3.6, built on Win XP with MinGW. By updating to 7.3.11 It builds fine to gvim.exe but building to vim.exe 7.3.11 gives: ... gcc

Re: Patch 7.3.008

On 23/09/2010 09:49 a.m., Onur Küçük wrote: On Thu, 23 Sep 2010 08:18:23 -0500 Cesar Romanicesar.rom...@gmail.com wrote: I'm using vim 7.3.6, built on Win XP with MinGW. By updating to 7.3.11 It builds fine to gvim.exe but building to vim.exe 7.3.11 gives: ... gcc

Building the latest vim 7.3 failed to compile on Win XP with MinGW

I'm getting following error: gcc ... -o uninstal.exe uninstal.c -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl32 -lversion -lwsock32 -Lc:/tcl/lib -ltclstub85 C:\DOCUME~1\Romer\IMPOST~1\Temp\ccYnj5jw.o:uninstal.c:(.text+0x24): undefined reference to

  1   2   >