On 13/03/10 10:02, Peter Thomas wrote:
I'm trying to build a version of vim with perl support that will run
under the cygwin terminal (ie. *not* the win32 build). The configure/
make/make install sequence runs to completion with no errors, however
when I fire up vim and do a test perl command like ":perl 'my $i=1;'",
vim quits with this message:
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault
Versions used:
- latest cygwin as of this post (setup.exe v2.686)
- vim 7.2 sources (runtime, lang, and extras), applied patches 001
through 394
- Perl 5.10.1-3 (the one that comes with cygwin)
Steps followed:
- open a cygwin terminal...
- download, unzip and patch vim sources from vim.org
- cd vim72/src
- run './configure --enable-perlinterp --prefix=/opt/vimtest' (to
avoid interfering with cygwin's pre-existing vim)
- run 'make&& make install'
- run '/opt/vimtest/bin/vim.exe'
- try a ":perl" command -> observed segfault
Is there something I've overlooked? Can someone please point me in the
right direction, either to fix or to troubleshoot?
Thanks very much,
Peter
Running configure separately is dangerous if the "requirements" of the
Makefile have been modified, because in that case "make" will rebuild
the Makefile, running configure in the process (without your handcrafted
command-line arguments).
I recommend to set configure arguments via environment variables passed
to make, see http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
for an example.
I'm not saying that this is necessarily your problem, but it could be,
since you applied quite a number of patches and some of them modify one
or more of Makefile, auto/configure, config.mk etc.
Also, if configure has a problem, it will return a nonzero exit code,
and in that case (if configure was invoked by make) the "compile" step
will not be launched. The config log should tell you what went wrong (I
recommend logging the console messages from configure and make via tee,
but a more detailed config.log is put in the src/auto directory; I
usually don't need that much detail to know what went wrong.
To reconfigure and recompile, use either
make reconfig
(one step) or
make config
make
(two steps), in both cases after setting the proper environment variables.
Best regards,
Tony.
--
FIRST HEAD: All right! All right! We'll kill him first and then have tea and
biscuits.
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
--
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
