On 08/04/2013 02:07 PM, Bram Moolenaar wrote:
> How about only using the VERSION when the other one is empty? Does this
> work for you or generate some error (in src/auto/configure):
>
> rubyversion=`$vi_cv_path_ruby -r rbconfig -e "print
$ruby_rbconfig::CONFIG['ruby_version'].gsub(/\./, '
Michael Henry wrote:
> On Fedora 19, Vim's configure script no longer correctly detects
> the version of Ruby. Vim's current algorithm involves the Ruby
> expression ``RbConfig::CONFIG['ruby_version']``, which returns a
> string such as "1.9.1" on Fedora 17. On Fedora 19, the above
> Ruby expre
Michael Henry wrote:
> On 08/03/2013 08:59 PM, James McCoy wrote:
> > Notice how the version number here doesn't match the version number in
> > the previous command? RbConfig::CONFIG['ruby_version'] reports the API
> > version, while VERSION/RUBY_VERSION report the release version.
> >
> > $ ru
On 08/03/2013 08:59 PM, James McCoy wrote:
> Notice how the version number here doesn't match the version number in
> the previous command? RbConfig::CONFIG['ruby_version'] reports the API
> version, while VERSION/RUBY_VERSION report the release version.
>
> $ ruby --version
> ruby 1.9.3p194 (2012
On Sat, Aug 03, 2013 at 08:29:06PM -0400, Michael Henry wrote:
> Empirically, I can verify that the behavior has changed. On
> Fedora 17, the query works:
>
> $ ruby -r rbconfig -e "puts RbConfig::CONFIG['ruby_version']"
> 1.9.1
>
> On Fedora 19, this same query prints the empty string.
>
>
All,
On Fedora 19, Vim's configure script no longer correctly detects
the version of Ruby. Vim's current algorithm involves the Ruby
expression ``RbConfig::CONFIG['ruby_version']``, which returns a
string such as "1.9.1" on Fedora 17. On Fedora 19, the above
Ruby expression returns an empty stri