On Wednesday, February 17, 2016 at 8:48:46 PM UTC+1, Bram Moolenaar wrote:
> Does anyone know how to avoid these warnings?
This should help:
https://gcc.gnu.org/wiki/VerboseDiagnostics#delete-non-virtual-dtor
PS: you also have this one:
gui_dwrite.cpp:348:13: warning: deleting object of polymorp
Console version fails to compile.
eval.c:14539: undefined reference to `get_job_options'
because it's defined inside #ifdef FEAT_CHANNEL
--
--
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
On Monday, February 15, 2016 at 11:24:47 PM UTC+1, Michael Giuffrida wrote:
> When building on windows with 7.4.1327:
> os_win32.c(5074) : error C2065: 'saAttr' : undeclared identifier
> os_win32.c(5077) : error C2065: 'ifd' : undeclared identifier
> os_win32.c(5079) : error C2065: 'ofd' : undeclar
On Sunday, February 14, 2016 at 11:02:55 PM UTC+1, Bram Moolenaar wrote:
> Patch 7.4.1319 (after 7.4.1318)
> Problem:Tests fail on MS-Windows and on Unix with GUI.
> Solution: Fix unregistering.
> Files: src/structs.h, src/channel.c, src/os_unix.c, src/os_win32.c,
> src/proto
On Thursday, May 28, 2015 at 9:35:49 PM UTC+2, David Fishburn wrote:
> New machine, a newer installation of VS.
>
>
>
>
>
> > "C:\Program Files\Mercurial\hg.exe" pull
> pulling from https://vim.googlecode.com/hg/
> searching for changes
> no changes found
>
>
>
>
>
> > "C:\Program Files (
On Thursday, May 7, 2015 at 3:20:27 AM UTC+2, Bram Moolenaar wrote:
> Or perhaps we can merge the Make_cyg and Make_ming makefiles in the
> src/GvimExt subdirectory? Like we did in the src directory.
> Would be good if someone who has both can make a patch.
Actually, I don't think src/GvimExt/Mak
On Wednesday, May 6, 2015 at 6:53:59 AM UTC+2, Bram Moolenaar wrote:
> > Had a similar problem, fixed it by adding -lgdi32 to LIBS (line 50) in
> > GvimExt\Make_ming.mak.
>
> I'll assume that works for everyone.
Quite possible Make_cyg.mak would require a similar change.
--
--
You received th
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 -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
> w
On Tuesday, April 21, 2015 at 9:39:41 PM UTC+2, tux. wrote:
> Bram Moolenaar schrob am Dienstag, 21. April 2015 um 15:25 Zeit:
>
> > Patch 7.4.705
> > Problem:Can't build with Ruby 2.2.
>
> Hmm.
>
> > if_ruby.obj : error LNK2001: Nicht aufgelöstes externes Symbol
> > "_rb_gc_writebarrier_unp
On Monday, April 20, 2015 at 3:31:09 PM UTC+2, tux. wrote:
> Am 2015-04-19 18:53, schrieb Claudia Hardman:
>
> > Tested with tuxproject 7.4.699 x64, and also with precompiled 7.4.691
> > x64 from
> > [veegee](https://bintray.com/veegee/generic/vim_x64/view#files),
> > platform Windows 7. Lua 5.3 a
> I'm using Windows 8.1 64-bit and VS2013.
>
> I couldn't build with the makefile at all. I got an error for a missing
> file.
Win32.mak by any chance? If you use community edition then SDK should be
included, just:
set INCLUDE=%INCLUDE%;c:\Program Files (x86)\Microsoft
SDKs\Windows\v7.1A\In
On Sunday, April 5, 2015 at 3:01:29 PM UTC+2, Bram Moolenaar wrote:
> Thanks for the patch. Why do you call it a workaround? Would there be
> a better way to fix this?
A bad choice of a word. It was a quick fix around the problem I was having when
I was compiling Vim, but I don't see a better w
C API changed in Ruby 2.2:
rb_num2long now returns a long instead of SIGNED_VALUE and
rb_num2ulong returns an unsigned long instead of VALUE.
As a consequence Vim fails to compile (tried to build a version with dynamic
Ruby; MinGW x64 under Windows) with the following errors:
if_ruby.c:399:14:
On Friday, September 19, 2014 7:25:56 PM UTC+2, KF Leong wrote:
> >
> > but this works and installs Vim in C:\testvim6\vim\vim74\vim.exe:
> >
> > gvim74-442.exe /S /D=C:\testvim6\vim
>
> Test with "/S /D=C:\vim" or "/S /D=D:\vim" works...
> The script expects the final path should be \vim !!! ;D
On Thursday, September 18, 2014 10:14:45 PM UTC+2, Tim Lebedkov wrote:
> unfortunately still does not work for me on Windows 2008 R2 Datacenter
>
> with "/S" or "/S /D". The exit code is 0.
You could perhaps try this with the original NSIS file: Replace "Function
.onInit" line with the following
On Wednesday, September 17, 2014 3:36:52 PM UTC+2, KF Leong wrote:
> On Tuesday, September 16, 2014 4:37:43 AM UTC+8, Tim Lebedkov wrote:
> > The installer works also on Windows 2008 R2 Datacenter, but the silent
> >
> > installation does not work at all (neither /S nor /D)
> >
> >
> Hmm... test
On Sunday, September 14, 2014 5:13:38 AM UTC+2, Andrei Olsen wrote:
> On Saturday, September 13, 2014 3:50:40 PM UTC+2, Tim Lebedkov wrote:
> > Hello,
> >
> > the following command does not work as expected and installs Vim in
> > C:\Program Files (x86)\vim\vim74:
&
On Saturday, September 13, 2014 3:50:40 PM UTC+2, Tim Lebedkov wrote:
> Hello,
>
> the following command does not work as expected and installs Vim in
> C:\Program Files (x86)\vim\vim74:
>
> "%setup%" /S /D=%CD%
>
> --
/D= sets $InstDir before .onInit script code is called, so it doesn't work
On Tuesday, October 8, 2013 10:02:30 PM UTC+2, cyboman wrote:
> On Tuesday, October 8, 2013 3:28:41 PM UTC-4, Andrei Olsen wrote:
> > On Tuesday, October 8, 2013 6:02:59 PM UTC+2, cyboman wrote:
> > > I can't compile Vim for Windows 7 using MinGW.
> > >
>
On Tuesday, October 8, 2013 6:02:59 PM UTC+2, cyboman wrote:
> I can't compile Vim for Windows 7 using MinGW.
>
> Here is the command I'm using
>
> mingw32-make.exe -f Make_ming.mak ARCH=x86-64 FEATURE=HUGE OLE=yes
> PYTHON3=C:/Python32 DYNAMIC_PYTHON3=yes PYTHON3_VER=32 gvim.exe 2>&1 | tee
> v
On Friday, September 27, 2013 6:51:49 PM UTC+2, tild...@gmail.com wrote:
> I followed a link (http://aufather.wordpress.com/2010/08/15/building-gvim/)
> to compile vim (without root login). When I ran ./configure --prefix=$PREFIX
> --host=$HOST --build=$BUILD I got error as below:
>
> =
On Sunday, August 4, 2013 2:12:28 AM UTC+2, Bohr Shaw wrote:
> This is a the left and bottom part of the whole screen picture.
This is probably related to this discussion:
https://groups.google.com/d/topic/vim_dev/ODi7rQPQdTw/discussion
--
--
You received this message from the "vim_dev" maillis
On Tuesday, July 9, 2013 3:50:20 PM UTC+2, David Fishburn wrote:
> I believe I saw this fixed earlier, or something related.
>
>
> I have tested this with:
>
> :ver
> VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 9 2013 09:34:36)
>
> MS-Windows 32-bit GUI version with OLE support
> Inc
> Anyway I found the cause: it is Python that is broken, not Vim. If Python3 is
> installed properly (as opposed to python3X.dll simply copied over),
> everything works.
You'd need a Python standard library along with your pythonXY.dll, i.e. create
a pythonXY.zip with contents of your Python's
On Thursday, July 25, 2013 7:09:38 AM UTC+2, Sergey Khorev wrote:
> Hi,
>
>
> Apparently it's not only I who can't get Python3 support working in Windows
> (at least Win7 x64), neither dynamic nor static one, and neither x86 nor
> amd64. Here are options I tried:
>
>
>
>
>
> All of these b
On Saturday, June 22, 2013 9:28:46 AM UTC+2, JohnBeckett wrote:
> I wanted to update our tip[1] on building Vim in Windows with
>
> Visual Studio to use VS 2012 Express, as well as VSE2010.
>
>
>
> While doing that I noticed that there is a double percent (%%)
>
> in two batch files, and I'm p
Patch adds fail_if_missing test that was missing for Python 3.
diff -r c628346c7f96 src/configure.in
--- a/src/configure.in Thu Jun 13 22:59:30 2013 +0200
+++ b/src/configure.in Fri Jun 14 08:15:18 2013 +0200
@@ -1229,6 +1229,9 @@
AC_MSG_RESULT(too old)
fi
fi
+ if test "$fail_if
On Friday, June 14, 2013 3:36:44 AM UTC+2, Zulox4 wrote:
> Hello,
>
> When Vim 7.3.1189 win32 console start it display this error (the next five
> lines) :
>
> C:\Vim_20130614_1189\vim\src>vim
> Error detected while processing C:\Users\vim7user_win7sp1\.vimrc:
> line1:
> E518: Unknown option
On Monday, June 10, 2013 12:55:16 PM UTC+2, Bram Moolenaar wrote:
> On my work system I ran into problems when trying to build with both
>
> Python 2 and 3.
>
>
>
> The first error is:
>
>
>
> vim/src/if_python3.c:87: warning: "PyString_Check" redefined [enabled by
> default]
>
> 926 /usr
On Thursday, June 6, 2013 7:47:56 PM UTC+2, Ben Fritz wrote:
> On Wednesday, June 5, 2013 5:43:40 PM UTC-5, Andrei Olsen wrote:
> > On Thursday, June 6, 2013 12:32:41 AM UTC+2, Ben Fritz wrote:
> > > On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
> >
On Thursday, June 6, 2013 12:32:41 AM UTC+2, Ben Fritz wrote:
> On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
> > On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
> > > I found this stackoverflow post:
> > > http://stackoverflow.com/ques
On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
> I found this stackoverflow post:
> http://stackoverflow.com/questions/3373914/compiling-vim-with-python-support
>
> Which led me to look at src/auto/config.log
>
> Here I see something suspicious:
>
> configure:5416: checking if -
On Thursday, May 30, 2013 3:59:59 AM UTC+2, David Fishburn wrote:
> Windows 7 64.
>
>
> :ver
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 29 2013 18:37:51)
>
> MS-Windows 32-bit GUI version with OLE support
> Included patches: 1-1053
> +python3/dyn
>
>
>
> Python 3.3.0
>
>
>
> I
On Wednesday, May 29, 2013 7:11:13 PM UTC+2, Axel Bender wrote:
> I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on Windows
> 7 (64 bits). Python 2.7 (64 bits) works from the command line.
>
> :py print "hello" gives me
>
> E448: Could not load library function Py_InitModule4
kl. 04:17:42 UTC+2 mandag 20. mai 2013 skrev Ben Fritz følgende:
> I'm using the "Vim without Cream" build, version 7.3.822, on Windows 7 64-bit.
>
> And cmd.exe really does stop responding when I pass gvim the -f flag. No
> prompt appears until Vim closes. Any typing done in the cmd.exe window d
> > 2. 64-bit WinPE does not have a WOW64 subsystem, hence you cannot run
> > a 32-bit executable.
>
> What is WinPE?
Windows Preinstallation Environment
http://en.wikipedia.org/wiki/Windows_Preinstallation_Environment
http://technet.microsoft.com/en-us/library/hh825110.aspx
Basically, a live
> For me compiling ruby with visual studio was the way to go since I have tried
> to build with mingw and python and for some reason it did not link correctly
> (the 32 bit version works fine).
Oh, I forgot that I had a slightly modified make file. It will work if you add
-DMS_WIN64
to DEFINES
kl. 23:40:01 UTC+2 tirsdag 21. mai 2013 skrev skeept følgende:
> Well, I have downloaded the 64 bit 2.0-p195 rubyinstaller from
> http://rubyinstaller.org/downloads/
> and configured ruby with
> RUBY="C:\htemp\Ruby200-x64" DYNAMIC_RUBY=yes RUBY_VER=20 RUBY_VER_LONG=2.0.0 ^
>
> when compiling I g
38 matches
Mail list logo
