Hi,
It seems that the rb_defout symbol was removed a couple of days ago.
This has broken VIM if Ruby support is compiled in with
–enable-rubyinterp. An existing VIM binary will no longer work, whereas
compiling a new one fails.
Ian
–
Ian Macdonald | If you marry a man who cheats on his wife,
System Administrator | you’ll be married to a man who cheats on
ian@caliban.org | his wife. – Ann Landers
http://www.caliban.org |
>
Ian Macdonald wrote: [Tue Jul 29 2003, 02:48:56AM EDT]
It seems that the rb_defout symbol was removed a couple of days ago.
This has broken VIM if Ruby support is compiled in with
–enable-rubyinterp. An existing VIM binary will no longer work,
whereas compiling a new one fails.
Indeed, I’ve found the same thing. I’m not familiar with Ruby
internals, but I’m hoping Shugo Maeda will step forward to fix it for
us. 
Aron
See http://article.gmane.org/gmane.editors.vim.devel/4088 for a patch to
fix this problem. Based on the cvs commit log for ruby, I modified the
vim-ruby interface to use rb_stdout instead of rb_defout in all cases.
If this was incorrect, hopefully somebody will speak up! 
Aron