On Sun, 7 Jun 2009 18:29:36 +0700 Emmanuel Benisty <benisty.e@xxxxxxxxx> wrote: > On Sun, Jun 7, 2009 at 6:10 PM, Allan McRae<allan@xxxxxxxxxxxxx> > wrote: > > Emmanuel Benisty wrote: > >> > >> On Sun, Jun 7, 2009 at 11:47 AM, Allan McRae<allan@xxxxxxxxxxxxx> > >> wrote: > >> > >>> > >>> Hi all, > >>> > >>> I have built ruby-1.9.1 for [testing]. As far as I can tell, > >>> the only thing that is broken is gvim. A dev who uses that will > >>> want to look into fixing it... I hear there is a patch floating > >>> around for ruby-1.9 support > >>> but not sure if it is now included upstream. You can always use > >>> IgnorePkg > >>> until it is fixed. > >>> > >>> (Lets see if gvim users complain more than the ruby users have...) > >>> > >> > >> FTR, it breaks vim too here. > >> vim: error while loading shared libraries: libruby.so.1.8: cannot > >> open shared object file: No such file or directory > >> > > > > That is because vim appears to turn into gvim when you install > > gvim. So still only gvim is broken. > > Thanks Allan. > > I removed gvim and vim works "again" indeed. That's was a bit > confusing. I actually made a patch against vim/gvim: http://pastr.it/pastes/view/16202/pastr_16202.diff Since applying it, I'm using Ruby 1.9 from svn and it works very well, had to compile vi/vim/gvim with the same patchlevel though. In the PKGBUILD, the patch should be applied before configure runs, maybe someone can propose it upstream, I haven't found a vim bugtracker yet. -- ^ manveru
