Hello,
James McCoy wrote:
> What about just disabling the Perl bindings on kfreebsd-any for now?
If you'd be happy to do that, yes please. But keeping the bug open.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
On Fri, Nov 04, 2016 at 01:39:35PM +, Steven Chamberlain wrote:
> Hi,
>
> If you've no objection, I may build vim on the kfreebsd-* porterboxes
> with DEB_BUILD_OPTIONS=nocheck, and binNMU the result.
What about just disabling the Perl bindings on kfreebsd-any for now?
Cheers,
--
James
GPG
Hi,
If you've no objection, I may build vim on the kfreebsd-* porterboxes
with DEB_BUILD_OPTIONS=nocheck, and binNMU the result.
The problem would still be there, and it would be RC-severity if
kfreebsd were part of the stable release, but it's currently not.
Doing this would fix debootstrap of
On Sat, Oct 15, 2016 at 02:14:21PM -0400, James McCoy wrote:
> On Sat, Oct 15, 2016 at 01:40:43PM -0400, James McCoy wrote:
> > Lo and behold, configuring without --enable-perlinterp but adding
> > "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" to PERL_CFLAGS in
> > src/auto/config.mk reproduces
Control: tag -1 help
On Sun, Oct 16, 2016 at 12:27:13AM +0100, Steven Chamberlain wrote:
> Hi!
>
> I was about finished for the night, but then I thought to recompile
> option.c this way:
>
> $ cd src/vim-gtk
> $ touch option.c
> $ make PERL_CFLAGS="$(perl -MExtUtils::Embed -e ccopts) -g -O0
>
Hi!
I was about finished for the night, but then I thought to recompile
option.c this way:
$ cd src/vim-gtk
$ touch option.c
$ make PERL_CFLAGS="$(perl -MExtUtils::Embed -e ccopts) -g -O0
-fno-omit-frame-pointer"
| gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
In case it is helpful to know this later:
1561 100852 vim 0.016031 NAMI "/home/stevenc/vim-8.0.0022/src/vim-gtk/po"
1561 100852 vim 0.016033 RET __getcwd 0
1561 100852 vim 0.016065 CALL break(0x136b000)
1561 100852 vim 0.016071 RET break 0
1561 100852 vim
James McCoy wrote:
> Lo and behold, configuring without --enable-perlinterp but adding
> "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" to PERL_CFLAGS in
> src/auto/config.mk reproduces the issue.
[...]
> Which begs the question, why does configure think the defines aren't
> necessary?
That seems
James McCoy wrote:
> And why does Perl's build think they are necessary, advertising them as
> required to build against Perl?
Even in Linux architectures (amd64 and armhf for example) Perl
advertises -D_LARGEFILE_SOURCE as a necessary compiler flag:
$ perl -MExtUtils::Embed -e ccopts
James McCoy wrote:
> Lo and behold, configuring without --enable-perlinterp but adding
> "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" to PERL_CFLAGS in
> src/auto/config.mk reproduces the issue.
Thanks, I did miscompile vim-gtk before and came to the wrong
conclusion about -fwrapv
> Which begs
On Sat, Oct 15, 2016 at 01:40:43PM -0400, James McCoy wrote:
> On Sat, Oct 15, 2016 at 03:41:07PM +0100, Steven Chamberlain wrote:
> > Steven Chamberlain wrote:
> > > If I override that flag with -fno-wrapv:
> > >
> > > + $(CCC) $(LUA_CFLAGS) $(PERL_CFLAGS) -fno-wrapv $(PYTHON_CFLAGS)
> > >
On Sat, Oct 15, 2016 at 03:41:07PM +0100, Steven Chamberlain wrote:
> Steven Chamberlain wrote:
> > If I override that flag with -fno-wrapv:
> >
> > + $(CCC) $(LUA_CFLAGS) $(PERL_CFLAGS) -fno-wrapv $(PYTHON_CFLAGS)
> > $(PYTHON3_CFLAGS) $(RUBY_CFLAGS) $(TCL_CFLAGS) -o $@ option.c
> >
> > then
Steven Chamberlain wrote:
> If I override that flag with -fno-wrapv:
>
> + $(CCC) $(LUA_CFLAGS) $(PERL_CFLAGS) -fno-wrapv $(PYTHON_CFLAGS)
> $(PYTHON3_CFLAGS) $(RUBY_CFLAGS) $(TCL_CFLAGS) -o $@ option.c
>
> then it no longer segfaults, and all vim-gtk tests pass :)
Or, I possibly
Hi!
James McCoy wrote:
> That pattern continued and Vim patch 7.4.1065[0] appears to be what
> broke Vim for kFreeBSD.
Thanks for narrowing it down to that patch. Most of it only relates
to --enable-perlinterp=dynamic and not to --enable-perlinterp[=yes] so
the changes are mostly no-ops...
On Thu, Oct 13, 2016 at 09:08:17PM -0400, James McCoy wrote:
> On Thu, Oct 13, 2016 at 08:27:12PM -0400, James McCoy wrote:
> > On Thu, Oct 13, 2016 at 07:37:13PM -0400, James McCoy wrote:
> > > However, I was currently looking into a different test failure whose
> > > symptom is that ":set
On Thu, Oct 13, 2016 at 08:27:12PM -0400, James McCoy wrote:
> On Thu, Oct 13, 2016 at 07:37:13PM -0400, James McCoy wrote:
> > However, I was currently looking into a different test failure whose
> > symptom is that ":set modified" doesn't actually do anything.
>
> Interesting. This has
On Thu, Oct 13, 2016 at 07:37:13PM -0400, James McCoy wrote:
> However, I was currently looking into a different test failure whose
> symptom is that ":set modified" doesn't actually do anything.
Interesting. This has something to do with enabling the language
bindings. When compiling with the
On Fri, Oct 14, 2016 at 12:08:46AM +0100, Steven Chamberlain wrote:
> Hi,
>
> James McCoy wrote:
> > I've solved the fifo test failure, and now am able to see the segfault
> > on fischer. However, gdb has been pretty useless for me on kfreebsd.
> >
> > Is there something else that I should try
Steven Chamberlain wrote:
> I didn't see a segfault yet on fischer, only this:
Never mind, I can reproduce it with
~/vim-8.0.0022/src/vim-gtk/po$ ktrace -di -- ../vim -u NONE -e -X -S check.vim
-c "if error == 0 | q | endif" -c cq af.po
I'm reading over the kdump output now.
I'm not sure
I didn't see a segfault yet on fischer, only this:
| From test_channel.vim:
| Found errors in Test_communicate():
| function
|
RunTheTest[9]..Test_communicate[2]..5_run_server[1]..RunServer[21]..Ch_communicate
| line 26: Expected 'ok' but got ''
| function
|
Hi,
James McCoy wrote:
> I've solved the fifo test failure, and now am able to see the segfault
> on fischer. However, gdb has been pretty useless for me on kfreebsd.
>
> Is there something else that I should try using instead?
I would usually enable core dumps and look at those in gdb first,
On Sat, Oct 01, 2016 at 08:33:54PM -0400, James McCoy wrote:
> On Sat, Oct 01, 2016 at 10:48:47PM +0100, Steven Chamberlain wrote:
> > But now, a new error is being seen on kfreebsd and interestingly, also
> > on linux-alpha:
> >
> > | Found errors in Test_tagcase():
> > | Caught exception in
On Sat, Oct 01, 2016 at 10:48:47PM +0100, Steven Chamberlain wrote:
> Hi,
Hi!
> The error is slightly different now.
>
> Test_communicate was fixed upstream:
> | 1621 7.4.2154 Test_communicate() fails sometimes
Well, worked around. That just marks the test as flaky, so it'll get
retried
retitle 827319 vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed
found 827319 src:vim/2:7.4.2330-1
thanks
Hi,
The error is slightly different now.
Test_communicate was fixed upstream:
| 1621 7.4.2154 Test_communicate() fails sometimes
But now, a new error is being seen on kfreebsd and
24 matches
Mail list logo
