|
From: LaMont J. <la...@hp...> - 2002-02-15 20:39:25
|
> Ok, here's the final word from the Ruby gurus. > > It's a bug in the Ruby headers. It needs a fix in Ruby which has been > done in the Ruby development branch (Ruby 1.7.something) but not in > the current release (or at least not the one in Woody. I don't know > which version of Ruby you have in... wait, what was the name of the > character now? Well, unstable anyway) > It also needs a minor fix in SWIG which has been done in CVS but > wasn't released either. > > The bottom line is, we're out in the cold :( > Architectures with gcc 3.0.x are ruled out for the time being. ruby_1.6.6-5 is in sid (which will always be unstable) Depending on how invasive the fix is, I suppose the ruby maintainer could port the fix back to ruby 1.6.6-5, and thereby fix all these ruby-dependants. Akira? lamont |