On 22/05/2010 09:50 a.m., Tony Mechelynck wrote: > On 22/05/10 15:57, Cesar Romani wrote: >> It compiled fine until May 18. with ruby 1.9.1 on Win XP with MinGW. >> Now I'm getting this: >> >> -------------------- >> gobjZ/if_ruby.o:if_ruby.c:(.text+0x916): undefined reference to >> `rb_str_new_cstr' >> gobjZ/if_ruby.o:if_ruby.c:(.text+0xaf1): undefined reference to >> `rb_str_new_cstr' >> gobjZ/if_ruby.o:if_ruby.c:(.text+0xcd5): undefined reference to >> `rb_str_new_cstr' >> gobjZ/if_ruby.o:if_ruby.c:(.text+0xd94): undefined reference to >> `rb_str_new_cstr' >> gobjZ/if_ruby.o:if_ruby.c:(.text+0xf75): undefined reference to >> `rb_str_new_cstr' >> gobjZ/if_ruby.o:if_ruby.c:(.text+0x1145): more undefined references to >> `rb_str_new_cstr' follow >> collect2: ld returned 1 exit status >> make: *** [gvim.exe] Error 1 >> -------------------- > > I don't see that label in the if_ruby.c source, but maybe it is in one > of the included files. Is cscope usable on your system? If it is, you > could use it to track where rb_str_new_cstr is used; see > http://vim.wikia.com/wiki/Cscope for details. > > I'm compiling gvim with ruby on Linux with no problems, but it's only > ruby 1.8. > > Oh, and BTW, which 7.3a version are you compiling? Do you have a rough > estimate of the point where the regression happened? I see that Bram > committed a changeset (the latest so far) about 7 minutes before you > posted this mail, but it changed only gui.c plus two helpfiles. The > changesets before that were (in reverse chronological order) a > runtime-files updates and the extra float functions patch (to eval.c) > pioneered by Bill McCarthy.
It was compiling fine until changeset 2188:014a996ac896, afterwards not anymore. Best regards, Cesar -- 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
