thank you everyone, especially christian
--
--
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 the
On Di, 13 Aug 2024, tooth pik wrote:
> my gcc is 7.5.0 with no higher option
>
> i will upgrade my os, i promise...
yes, you really should. You are on an unsupported platform for quite a
while already and do not receive security updates.
Thanks,
Christian
--
<``Erik> 18,446,744,073,709,551,
my gcc is 7.5.0 with no higher option
i will upgrade my os, i promise...
On Tue, Aug 13, 2024 at 3:27 AM Christian Brabandt
wrote:
>
> On Di, 13 Aug 2024, Christian Brabandt wrote:
>
> > Hi,
> > I compiled my own Python3.6.8 version and tried to reproduce but
> > couldn't. I'd really recommend
On Di, 13 Aug 2024, Christian Brabandt wrote:
> Hi,
> I compiled my own Python3.6.8 version and tried to reproduce but
> couldn't. I'd really recommend to upgrade your system, considering that
> Python3.6 and Leap 15.4 is end-of-life already.
The same issue happened on the vim-appimage reposi
Hi,
I compiled my own Python3.6.8 version and tried to reproduce but
couldn't. I'd really recommend to upgrade your system, considering that
Python3.6 and Leap 15.4 is end-of-life already.
Thanks,
Chris
On Mo, 12 Aug 2024, tooth pik wrote:
> it happens during build
>
> not sure what log you
it happens during build
not sure what log you want to see so i'll start with 'myconfig':
#!/bin/bash
# myconfigure whacks the old config.cash so it always works
cd /home/toothpik/.build/vim/vim || exit 1
date '+%Y-%b-%d %H:%M' >> ../configure.log
rm -vf src/auto/config.cache | tee -a ../configur
Hi,
please show/attach the full log for (including the build-error):
./configure --with-features=huge --enable-python3interp=yes
--with-python3-stable-abi=3.6
And the error happens during compilation? Or when running Vim?
Thanks,
Chris
--
--
You received this message from the "vim_dev" maill
i don't know how to answer that
On Mon, Aug 12, 2024 at 2:48 AM Christian Brabandt
wrote:
>
> On So, 11 Aug 2024, tooth pik wrote:
>
> > that didn't take until i put a dot between the 3 and the 6
> >
> > it then took, but the build still failed in the same place
>
> So what patch introduced the
On So, 11 Aug 2024, tooth pik wrote:
> that didn't take until i put a dot between the 3 and the 6
>
> it then took, but the build still failed in the same place
So what patch introduced the problem? v9.1.0369 or v9.1.0368?
Mit freundlichen Grüßen
Christian
--
Love IS what it's cracked up to
in xterm drag the mouse to highlight, in your target hit the middle
mouse button -- any fool can paste from an xterm
if_python3.c
if_py_both.h: In function ‘ListItem’:
if_python3.c:312:24: error: dereferencing pointer to incomplete type
‘PyTypeObject {aka struct _typeobject}’
# define PySlice_Typ
that didn't take until i put a dot between the 3 and the 6
it then took, but the build still failed in the same place
On Sun, Aug 11, 2024 at 2:50 PM Christian Brabandt
wrote:
>
> On So, 11 Aug 2024, tooth pik wrote:
>
> > ooof -- i've been putting off the upgrade from suse 15.4 to 15.5, those
On So, 11 Aug 2024, tooth pik wrote:
> ooof -- i've been putting off the upgrade from suse 15.4 to 15.5, those
> upgrades
> can be such a pain -- as it stands, for the repositories i have, 3.6.15 is as
> good
> as it gets
What version did you compile? What are your compile settings? Have you
t
ooof -- i've been putting off the upgrade from suse 15.4 to 15.5, those
upgrades
can be such a pain -- as it stands, for the repositories i have, 3.6.15 is
as good
as it gets
On Sun, Aug 11, 2024 at 2:34 PM Christian Brabandt
wrote:
>
> On So, 11 Aug 2024, tooth pik wrote:
>
> > my python is 3.6
On So, 11 Aug 2024, tooth pik wrote:
> my python is 3.6.15
>
> my os is opensuse 15.4
>
> i am attaching a screen grab of the error, i seem to have forgotten how to use
> clipboard
> in x11
python 3.6 is end of life for some time already. Can you try an updated
python 3 please? I'll check wi
my python is 3.6.15
my os is opensuse 15.4
i am attaching a screen grab of the error, i seem to have forgotten how to
use clipboard
in x11
On Sun, Aug 11, 2024 at 2:24 PM Christian Brabandt
wrote:
>
> On So, 11 Aug 2024, tooth pik wrote:
>
> > something broke my python3/dyn build
> >
> > in fu
On So, 11 Aug 2024, tooth pik wrote:
> something broke my python3/dyn build
>
> in function ListItem
> if_python3.c 312:24 error: dereferencing pointer to incomplete type
> 'PyTypeObject'
what version is this? What python3 version are you using?
Thanks,
Christian
--
"There is such a fine l
something broke my python3/dyn build
in function ListItem
if_python3.c 312:24 error: dereferencing pointer to incomplete type
'PyTypeObject'
--
--
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, v
patch 9.0.2087: build-failure in vim9class
Commit:
https://github.com/vim/vim/commit/33c1da7ff49c3ccdce3a6d98bd620e324c5cd6ff
Author: Christian Brabandt
Date: Thu Nov 2 22:45:12 2023 +0100
patch 9.0.2087: build-failure in vim9class
Problem: build-failure in vim9class
For example in Normal build:
In file included from vim.h:570,
from vim9class.c:15:
vim9class.c: In function ‘ex_class’:
vim9class.c:1563:24: error:
‘e_abstract_must_be_followed_by_def_or_static’ undeclared (first use
in this function); did you mean ‘e_abstract_must_be_followed_by_
patch 9.0.1721: Build failure on Windows with dynamic lua
Commit:
https://github.com/vim/vim/commit/4112acae0816e3f64c082b1e773dd5f4a100685e
Author: zeertzjq
Date: Wed Aug 16 07:29:28 2023 +0800
patch 9.0.1721: Build failure on Windows with dynamic lua
Problem: Build failure on
gobjx86-64/if_perl.o] Error 1
Error by compiling gvim.exe
Regards,
--
Cesar
On Wednesday, August 9, 2023 at 1:15:08 PM UTC-5 Christian Brabandt wrote:
> patch 9.0.1681: Build Failure with Perl 5.38
>
> Commit:
> https://github.com/vim/vim/commit/1d7caa58e3c87f75a4becbceabb
patch 9.0.1681: Build Failure with Perl 5.38
Commit:
https://github.com/vim/vim/commit/1d7caa58e3c87f75a4becbceabbd1af181ace11e
Author: Philip H <47042125+pheid...@users.noreply.github.com>
Date: Thu Jun 22 08:55:47 2023 +0200
patch 9.0.1681: Build Failure with Perl 5.38
P
Tony wrote:
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
> -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
> -D_FORTIFY_SOURCE=3D1-o objects/window.o window.c
> window.c: In function =E2=80=98may_trigger_win_scrolled_resized=E2=80=99:
> window.c:313
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/window.o window.c
window.c: In function ‘may_trigger_win_scrolled_resized’:
window.c:3137:27: error: ‘scroll_dict’ undeclared (firs
Tony wrote:
> linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
> status' $? ; date) 2>&1 |tee -a make.log
> [=E2=80=A6]
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
> -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
> -D_FORTIFY_SOURCE=
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
[…]
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/cmdexpand.o cmd
I get the following in Small and Tiny at patchlevel 8.2.4014 (other
builds are OK):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
-Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/option.o option.c
In file included
Tony wrote:
> Only the Huge build succeeds but there are two different kinds of
> failures in the other four:
It appears some #ifdef are misplaced. Patch coming...
--
hundred-and-one symptoms of being an internet addict:
171. You invent another person and chat with yourself in empty chat roo
Only the Huge build succeeds but there are two different kinds of
failures in the other four:
1) In Small and Tiny:
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
On 2021-10-24, Bram Moolenaar wrote:
> On 2021-10-18, Gary Johnson wrote:
>
> [...]
>
> > > I read auto/configure more carefully to understand it better. Then
> > > I copied conftest.c for that test to another directory and
> > > successfully compiled it there with
> > >
> > > #define ST_MTI
On 2021-10-18, Gary Johnson wrote:
[...]
> > I read auto/configure more carefully to understand it better. Then
> > I copied conftest.c for that test to another directory and
> > successfully compiled it there with
> >
> > #define ST_MTIM_NSEC st_mtim.tv_nsec
> >
> > So I should be able to
On 2021-10-18, Gary Johnson wrote:
> On 2021-10-18, Bram Moolenaar wrote:
> > Gary Johnson wrote:
> >
> > > > > On 2021-10-17, Dominique Pell=C3=A9 wrote:
> > > > > > Gary Johnson wrote:
> > > > > >
> > > > > > > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > > > > > > vario
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce
-Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1-o objects/optionstr.o optionstr.c
In file included from optionstr.c:14:0:
optionstr.c: In function ‘did_set_string_option’:
optionstr.c
On 2021-10-18, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > > > On 2021-10-17, Dominique Pell=C3=A9 wrote:
> > > > > Gary Johnson wrote:
> > > > >
> > > > > > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > > > > > various reasons. It's what I can run on that hardware.
Gary Johnson wrote:
> > > On 2021-10-17, Dominique Pell=C3=A9 wrote:
> > > > Gary Johnson wrote:
> > > >
> > > > > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > > > > various reasons. It's what I can run on that hardware. A recent
> > > > > update of Vim failed to build
On 2021-10-17, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > On 2021-10-17, Dominique Pell=C3=A9 wrote:
> > > Gary Johnson wrote:
> > >
> > > > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > > > various reasons. It's what I can run on that hardware. A recent
> > > > up
Gary Johnson wrote:
> On 2021-10-17, Dominique Pell=C3=A9 wrote:
> > Gary Johnson wrote:
> >
> > > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > > various reasons. It's what I can run on that hardware. A recent
> > > update of Vim failed to build. A git bisect narrowed
On 2021-10-17, Dominique Pellé wrote:
> Gary Johnson wrote:
>
> > I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> > various reasons. It's what I can run on that hardware. A recent
> > update of Vim failed to build. A git bisect narrowed it down to the
> > 8.2.3510 commit. He
Gary Johnson wrote:
> I have an older Ubuntu 10.04.4 system that I cannot upgrade for
> various reasons. It's what I can run on that hardware. A recent
> update of Vim failed to build. A git bisect narrowed it down to the
> 8.2.3510 commit. Here is the gcc command that failed.
>
>
> gcc -std=
I have an older Ubuntu 10.04.4 system that I cannot upgrade for
various reasons. It's what I can run on that hardware. A recent
update of Vim failed to build. A git bisect narrowed it down to the
8.2.3510 commit. Here is the gcc command that failed.
gcc -std=gnu99 -c -I. -Iproto -DHAVE_CONFIG
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-o objects/ex_getln.o ex_getln.c
ex_getln.c: In
After applying 8.2 patches 2680-2681, I get he following errors in
Tiny and Small:
linux-tuxedo:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-Wno-deprecated-declarations -U_F
Hi again
On Wednesday, 18 March 2020 11:39:03 UTC, Mike Williams wrote:
>
> Hi
>
> On Wednesday, 18 March 2020 11:01:22 UTC, Dominique Pelle wrote:
>>
>> Mike Williams wrote:
>>
>> > Hi,
>> >
>> > I am trying to build a terminal version of VIM that includes terminal
>> > support. My build lin
Hi
On Wednesday, 18 March 2020 11:01:22 UTC, Dominique Pelle wrote:
>
> Mike Williams wrote:
>
> > Hi,
> >
> > I am trying to build a terminal version of VIM that includes terminal
> > support. My build line run in the src directory are:
> >
> > nmake -nologo -f make_mvc.mak TERMINAL=yes FE
Mike Williams wrote:
> Hi,
>
> I am trying to build a terminal version of VIM that includes terminal
> support. My build line run in the src directory are:
>
> nmake -nologo -f make_mvc.mak TERMINAL=yes FEATURES=BIG
>
> The final link fails with:
>
> vterm_unicode.obj : error LNK2001: unresolved
Hi,
I am trying to build a terminal version of VIM that includes terminal
support. My build line run in the src directory are:
nmake -nologo -f make_mvc.mak TERMINAL=yes FEATURES=BIG
The final link fails with:
vterm_unicode.obj : error LNK2001: unresolved external symbol utf_uint2cells
vterm_u
Pawel Slowik wrote:
> Steps to reproduce:
> 1) on Linux,
> 2) run:
> ../configure --disable-netbeans --disable-xsmp --enable-gui=no
> 3) disable FEAT_SESSION:
> patch -p0 < /tmp/vim-disable-session.diff
> 4) compile:
> make
>
> Result:
> gcc -L/usr/local/lib -Wl,--as-needed-o vim obje
Steps to reproduce:
1) on Linux,
2) run:
../configure --disable-netbeans --disable-xsmp --enable-gui=no
3) disable FEAT_SESSION:
patch -p0 < /tmp/vim-disable-session.diff
4) compile:
make
Result:
gcc -L/usr/local/lib -Wl,--as-needed-o vim objects/arabic.o
objects/beval.o objects/buffer.o
Hi
On 14/12/2017 12:15, Bram Moolenaar wrote:
Mike Williams wrote:
I have just tried to bring my windows VIM builds up to date and find the
gvim build is failing with the following error:
gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
'dwrite_2.h': No such file or director
Mike Williams wrote:
> I have just tried to bring my windows VIM builds up to date and find the
> gvim build is failing with the following error:
>
> gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
> 'dwrite_2.h': No such file or directory
>
> This started with patch 1343 fo
Hi Mike,
2017/12/14 Thu 3:09:50 UTC+9 Mike Williams wrote:
> Hi,
>
> I have just tried to bring my windows VIM builds up to date and find the
> gvim build is failing with the following error:
>
> gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
> 'dwrite_2.h': No such file or
Hi,
I have just tried to bring my windows VIM builds up to date and find the
gvim build is failing with the following error:
gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
'dwrite_2.h': No such file or directory
This started with patch 1343 for colored emojis.
The file i
Kazunobu Kuriyama wrote:
> I tried Patch 7.4.2114 and found that the tiny build fails on OS X (That's
> not because of the patch, though).
>
> While the file os_macosx.m, which implements the clipboard support for OS
> X, is to be excluded from the source when --with-features=tiny
> (configure.i
Hi,
I tried Patch 7.4.2114 and found that the tiny build fails on OS X (That's
not because of the patch, though).
While the file os_macosx.m, which implements the clipboard support for OS
X, is to be excluded from the source when --with-features=tiny
(configure.in:4238--4258), vim.h:102 unconditi
On Fri, Jul 8, 2016 at 3:32 PM, Bram Moolenaar wrote:
>
> Tony Mechelynck wrote:
>
>> After upgrading my source from 7.4.1999 to 7.4.2000 my Tiny build
>> fails as follows:
[...]
>
> Thanks for the note. Probably forgot an #ifdef there.
7.4.2001 builds all right, even on Tiny. Thanks.
>
> --
>
Tony Mechelynck wrote:
> After upgrading my source from 7.4.1999 to 7.4.2000 my Tiny build
> fails as follows:
>
> linux-2iyu:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
> status' $? ; date) 2>&1 |tee -a make.log
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wa
After upgrading my source from 7.4.1999 to 7.4.2000 my Tiny build
fails as follows:
linux-2iyu:~/.build/vim/vim-hg/src/shadow-tiny # (make || echo 'exit
status' $? ; date) 2>&1 |tee -a make.log
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURC
Elimar Riesebieter wrote:
> [...]
>
> > > Well running this as user works as it should. So the only difference
> > > are the environment variables. My build wrapper has set LANG=C and
> > > LC_ALL=C. Setting LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 seems to
> > > solve the issue.
> > >
> > > It
* Bram Moolenaar [2016-02-28 14:20 +0100]:
>
> Elimar Riesebieter wrote:
[...]
> > Well running this as user works as it should. So the only difference
> > are the environment variables. My build wrapper has set LANG=C and
> > LC_ALL=C. Setting LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 seems to
Dominique Pellé wrote:
> Bram Moolenaar wrote:
>
> > Elimar Riesebieter wrote:
> >
> >> * Dominique Pellé [2016-02-28 12:08 +0100]:
> >>
> >> > Elimar Riesebieter wrote:
> >>
> >> [...]
> >> > Can you give us a backtrace with gdb?
> >>
> >> No. Can't find a core file anywhere.
> >>
> >> > You
I wrote:
> Elimar Riesebieter wrote:
>
> > * Dominique Pellé [2016-02-28 12:08 +0100]:
> >
> > > Elimar Riesebieter wrote:
> >
> > [...]
> > > Can you give us a backtrace with gdb?
> >
> > No. Can't find a core file anywhere.
> >
> > > You can get it from the core file using:
> > >
> > >
Bram Moolenaar wrote:
> Elimar Riesebieter wrote:
>
>> * Dominique Pellé [2016-02-28 12:08 +0100]:
>>
>> > Elimar Riesebieter wrote:
>>
>> [...]
>> > Can you give us a backtrace with gdb?
>>
>> No. Can't find a core file anywhere.
>>
>> > You can get it from the core file using:
>> >
>> > $ cd
Elimar Riesebieter wrote:
> * Dominique Pellé [2016-02-28 12:08 +0100]:
>
> > Elimar Riesebieter wrote:
>
> [...]
> > Can you give us a backtrace with gdb?
>
> No. Can't find a core file anywhere.
>
> > You can get it from the core file using:
> >
> > $ cd vim/src/testdir
> > $ make clean
Dominique Pelle wrote:
> Elimar Riesebieter wrote:
>
> > Hi all,
> >
> > I tried to build v7.4.1444 and got:
> >
> > (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L,
> > 0C written^M^M¬
> > Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L,
> > 521C^[[64;12H^[[K^[
* Dominique Pellé [2016-02-28 12:08 +0100]:
> Elimar Riesebieter wrote:
[...]
> Can you give us a backtrace with gdb?
No. Can't find a core file anywhere.
> You can get it from the core file using:
>
> $ cd vim/src/testdir
> $ make clean
> $ rm core
> $ make test_channel.res
Well running th
Elimar Riesebieter wrote:
> Hi all,
>
> I tried to build v7.4.1444 and got:
>
> (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C
> written^M^M¬
> Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L,
> 521C^[[64;12H^[[K^[[64;12H28L, 600C written^M^M¬
> ^[[?1l^[>^[[3
* Elimar Riesebieter [2016-02-28 10:44 +0100]:
> Hi all,
>
> I tried to build v7.4.1444 and got:
>
> (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C
> written^M^M¬
> Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L,
> 521C^[[64;12H^[[K^[[64;12H28L, 600C writt
Hi all,
I tried to build v7.4.1444 and got:
(1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C
written^M^M¬
Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L,
521C^[[64;12H^[[K^[[64;12H28L, 600C written^M^M¬
^[[?1l^[>^[[34h^[[?25h^[[?1049lVIMRUNTIME=../../runtime;
Hi,
2015/7/23 Thu 8:54:21 UTC+9 Raymond Ko wrote:
> Hello all,
>
> When I was running my own build script, I got the following error during link
> stage:
>
> unresolved external symbol __iob_func referenced in function OpenReadFile
>
> With some investigation, I found if I set XPM=no, then it
Hello all,
When I was running my own build script, I got the following error during link
stage:
unresolved external symbol __iob_func referenced in function OpenReadFile
With some investigation, I found if I set XPM=no, then it would link
successfully. Since I don't think I use XPM images for
Ken Takata wrote:
> When I build Vim with clang 3.5 and if_perl enabled on Cygwin, it fails with
> the following error:
>
> configure:5624: checking if compile and link flags for Perl are sane
> configure:5644: clang -o conftest.exe -O2 -fno-strength-reduce -Wall
> -DPERL_USE_SAFE_PUTENV -U__S
Hi,
When I build Vim with clang 3.5 and if_perl enabled on Cygwin, it fails with
the following error:
configure:5624: checking if compile and link flags for Perl are sane
configure:5644: clang -o conftest.exe -O2 -fno-strength-reduce -Wall
-DPERL_USE_SAFE_PUTENV -U__STRICT_ANSI__ -ggdb -O2 -pip
Michael Henry wrote:
> Because of changes in Fedora 20, Vim won't build with
> --enable-perlinterp. Back in Fedora 16, Perl's ExtUtils were
> found entirely in /usr/share/perl5/ExtUtils. The xsubpp utility
> was therefore found in /usr/share/perl5/ExtUtils/xsubpp. By
> Fedora 20, a portion of
All,
Because of changes in Fedora 20, Vim won't build with
--enable-perlinterp. Back in Fedora 16, Perl's ExtUtils were
found entirely in /usr/share/perl5/ExtUtils. The xsubpp utility
was therefore found in /usr/share/perl5/ExtUtils/xsubpp. By
Fedora 20, a portion of ExtUtils was moved into
/us
On Wed, Jul 17, 2013 at 12:36 PM, Manuel Ortega wrote:
> Hello,
>
> Just pulled 7.4a28, after having successfully build 7.4a.24.
>
> Build failed with this at the end:
>
> Undefined symbols for architecture x86_64:
> "_find_win_for_buf", referenced from:
> _RBAppend in if_python.o
> ld: sy
Hello,
Just pulled 7.4a28, after having successfully build 7.4a.24.
Build failed with this at the end:
Undefined symbols for architecture x86_64:
"_find_win_for_buf", referenced from:
_RBAppend in if_python.o
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit st
I just updated and tried to build, yeilding:
objects/if_python.o: In function `InsertBufferLines':
/home/name/.build/vim/vim/src/if_py_both.h:4018: undefined reference to
`find_win_for_buf'
/home/name/.build/vim/vim/src/if_py_both.h:4076: undefined reference to
`find_win_for_buf'
collect2: error
Kazunobu Kuriyama wrote:
> Attached are the patches fixing two different kinds of build failure
> on Mac, although both are about the compilation switch FEAT_CLIPBOARD.
>
> First, 'make' following ./configure --with-features=tiny --disable-gui
> yields the link error:
Hi,
Attached are the patches fixing two different kinds of build failure on Mac,
although both are about the compilation switch FEAT_CLIPBOARD.
First, 'make' following ./configure --with-features=tiny --disable-gui yields
the link error:
gcc -o vim objects/buffer
Yukihiro Nakadaira wrote:
> On Mon, May 20, 2013 at 4:37 AM, Christian J. Robinson
> wrote:
>
> > On Sun, 19 May 2013, Bram Moolenaar wrote:
> >
> >
> > Christian J. Robinson wrote:
> >>
> >> [..]/vim73/src/if_ruby.c:739: undefined reference to `ruby_init_stack'
> >>> collect2: ld returned 1
On Mon, May 20, 2013 at 6:49 PM, Yukihiro Nakadaira <
yukihiro.nakada...@gmail.com> wrote:
> On Mon, May 20, 2013 at 4:37 AM, Christian J. Robinson
> wrote:
>
>> On Sun, 19 May 2013, Bram Moolenaar wrote:
>>
>>
>> Christian J. Robinson wrote:
>>>
>>> [..]/vim73/src/if_ruby.c:739: undefined refe
On Mon, May 20, 2013 at 4:37 AM, Christian J. Robinson wrote:
> On Sun, 19 May 2013, Bram Moolenaar wrote:
>
>
> Christian J. Robinson wrote:
>>
>> [..]/vim73/src/if_ruby.c:739: undefined reference to `ruby_init_stack'
>>> collect2: ld returned 1 exit status
>>> link.sh: Linking failed
>>> make:
On Sun, 19 May 2013, Bram Moolenaar wrote:
Christian J. Robinson wrote:
[..]/vim73/src/if_ruby.c:739: undefined reference to `ruby_init_stack'
collect2: ld returned 1 exit status
link.sh: Linking failed
make: *** [vim] Error 1
What version of Ruby are you using? ruby_init_stack() is supposed
Christian J. Robinson wrote:
> I think reported this before, so it's been around for many
> patchlevels, but it's still outstanding. During linking:
>
> [..]/vim73/src/if_ruby.c:739: undefined reference to `ruby_init_stack'
> collect2: ld returned 1 exit status
> link.sh: Linking failed
> make:
I think reported this before, so it's been around for many
patchlevels, but it's still outstanding. During linking:
[..]/vim73/src/if_ruby.c:739: undefined reference to `ruby_init_stack'
collect2: ld returned 1 exit status
link.sh: Linking failed
make: *** [vim] Error 1
--
The xpm library from patch 639/640 is failing on me:
libXpm.lib(RdFToI.obj) : error LNK2001: unresolved external symbol __iob
libXpm.lib(parse.obj) : error LNK2001: unresolved external symbol __pctype
libXpm.lib(data.obj) : error LNK2001: unresolved external symbol __pctype
libXpm.lib(parse.obj) :
ug ug ug arg please I've given money to the Ugandan orphans I
want to cash in my karma now please someone
I just hg the latest as per vim home page still no luck building with
the perl interpreter,
though its a different error.
./configure works fine as before:
/configure --with-fea
Britton Kerin wrote:
> For the source from the download page I get this and the latest stable perl
> (5.12.3), I get this:
>
> $ ./configure --prefix=$HOME/local --enable-perlinterp=dynamic
> $ make
>
> [snip]
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
For the source from the download page I get this and the latest stable perl
(5.12.3), I get this:
$ ./configure --prefix=$HOME/local --enable-perlinterp=dynamic
$ make
[snip]
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/home/bkerin/local/include/gtk-2.0
-I/h
Birgi Tamersoy, 08.12.2008:
> Hello Everybody,
>
> I fixed this problem with a simple patch. I also had to add something to
> the Makefile. I decided to separate the Vim source tree patches related
> to CodeCheck from the direct code_check.c patches. That is why I am
> attaching two files. Please
Hello Markus,
On Tue, Dec 09, 2008 at 03:38:30AM +0100, Markus Heidelberg wrote:
>
> Currently the code_check.txt help file also has the *intro* and
> *progress* keywords which "overwrite" the default goals to intro.txt and
> the progress filetype. Could this be adjusted?
>
Yes, I can adjust th
Markus Heidelberg, 09.12.2008:
> Currently the code_check.txt help file also has the *intro* and
> *progress* keywords which "overwrite" the default goals to intro.txt and
> the progress filetype. Could this be adjusted?
I forgot to mention: after doing this, runtime/doc/tags could also be
update
Birgi Tamersoy, 09.12.2008:
>
> Hello Markus,
>
> On Tue, Dec 09, 2008 at 01:41:37AM +0100, Markus Heidelberg wrote:
> >
> > Birgi Tamersoy, 08.12.2008:
> > > Hello Everybody,
> > >
> > > I fixed this problem with a simple patch. I also had to add something to
> > > the Makefile. I decided to
Hello Markus,
On Tue, Dec 09, 2008 at 01:41:37AM +0100, Markus Heidelberg wrote:
>
> Birgi Tamersoy, 08.12.2008:
> > Hello Everybody,
> >
> > I fixed this problem with a simple patch. I also had to add something to
> > the Makefile. I decided to separate the Vim source tree patches related
> >
Birgi Tamersoy, 08.12.2008:
> Hello Everybody,
>
> I fixed this problem with a simple patch. I also had to add something to
> the Makefile. I decided to separate the Vim source tree patches related
> to CodeCheck from the direct code_check.c patches. That is why I am
> attaching two files. Please
Richard Hartmann, 08.12.2008:
>
> On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg
> <[EMAIL PROTECTED]> wrote:
>
> >> Markus, please put the attached file into the git repo.
> >
> > In which branch, master?
>
> Yes. That way, everyone will be able to see the README.
I've got it. I will put a R
Hello Everybody,
I fixed this problem with a simple patch. I also had to add something to
the Makefile. I decided to separate the Vim source tree patches related
to CodeCheck from the direct code_check.c patches. That is why I am
attaching two files. Please let me know if this is not a good idea,
On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg
<[EMAIL PROTECTED]> wrote:
>> Markus, please put the attached file into the git repo.
>
> In which branch, master?
Yes. That way, everyone will be able to see the README.
> I already have plans to split the readme part on the gitweb interface
> i
Birgi Tamersoy, 08.12.2008:
>
> Hello Markus,
>
> On Mon, Dec 08, 2008 at 01:10:20AM +0100, Markus Heidelberg wrote:
> >
> > Richard Hartmann, 07.12.2008:
> > > Hi all,
> > >
> > > building vim_extended with the code checker patch fails:
> > >
> > > code_check.c:315: error: 'gui' undeclared (
Hello Markus,
On Mon, Dec 08, 2008 at 01:10:20AM +0100, Markus Heidelberg wrote:
>
> Richard Hartmann, 07.12.2008:
> > Hi all,
> >
> > building vim_extended with the code checker patch fails:
> >
> >
> > % git checkout -b local/code_checking origin/vim
> > % git merge origin/code_checking
> >
1 - 100 din 106 matches
Mail list logo
