I've searched and only found one topic which did not have an answer or
explanation on how to install Ruby 1.9.1 Binary on windows.
Is there a "tutorial" or "documentation" on how to correctly install the
binary version on windows?
I find it hard to believe that some type of documentation would not be
available. There is no one-click installer for 1.9.1 so I don't mind
doing it the old fashioned way if I knew how to do so properly.
Thanks.
--
Posted via http://www.ruby-forum.com/.
This has been commented and discussed several times in this mailing
list by myself and my other developers.
You can go the mswin32 route which require you actualy READ the
install instructions at garbage collect site:
http://www.garbagecollect.jp/ruby/mswin32/en/
http://www.garbagecollect.jp/ruby/mswin32/en/documents/install.html
Or, to stay DRY with my answers:
http://blog.mmediasys.com/2009/05/05/rubyinstaller-state-of-one-click/
http://blog.mmediasys.com/2009/05/17/rubyinstaller-updated-packages-and-other-news/
http://blog.mmediasys.com/2009/05/19/pure-ruby-readline-released-012/
On May 27, 1:03 pm, Joel Dezenzio <jdezen...@gmail.com> wrote:
I've searched and only found one topic which did not have an answer or
explanation on how to install Ruby 1.9.1 Binary on windows.Is there a "tutorial" or "documentation" on how to correctly install the
binary version on windows?I find it hard to believe that some type of documentation would not be
available. There is no one-click installer for 1.9.1 so I don't mind
doing it the old fashioned way if I knew how to do so properly.
--
Luis Lavena
Is there a "tutorial" or "documentation" on how to correctly install the
binary version on windows?
Here's my crack at a tutorial.
This is to install versions built with mingw (i.e. pre releases for the
one click installer).
Cheers!
-=r
--
Posted via http://www.ruby-forum.com/\.
Here's my crack at a tutorial.
This is to install versions built with mingw (i.e. pre releases for
the
one click installer).
Cheers!
Hope it helps. For more information http://groups.google.com/group/trevor-hook
Regards,
Trevor.
On May 27, 9:03 am, Joel Dezenzio <jdezen...@gmail.com> wrote:
I've searched and only found one topic which did not have an answer or
explanation on how to install Ruby 1.9.1 Binary onwindows.Is there a "tutorial" or "documentation" on how to correctly install the
binary version onwindows?I find it hard to believe that some type of documentation would not be
available. There is no one-click installer for 1.9.1 so I don't mind
doing it the old fashioned way if I knew how to do so properly.Thanks.
--
Posted viahttp://www.ruby-forum.com/.
Hi Team,
I installed ruby 1.9.2, i am getting follwing error
This application has failed to start because msvcrt-ruby18.dll was not
found. Re-installing the application may fix this problem.
Do you want be to downgrade to 1.9. thanks for your help.
Regards
Srinivas P
--
Posted via http://www.ruby-forum.com/.
Roger Pack wrote:
Is there a "tutorial" or "documentation" on how to correctly install the
binary version on windows?Here's my crack at a tutorial.
This is to install versions built with mingw (i.e. pre releases for the
one click installer).
Programming gone awry: ruby 1.9 one click installer
Cheers!
-=r
Thanks Roger,
Can I ask one question though. If I have previously used the installer,
do I need to "uninstall" that version completely before installing the
ming/1.9 version?
I didn't see that in your link instructions so just wanted to confirm
before going forward with the test.
Thanks.
--
Posted via http://www.ruby-forum.com/\.
You're receiving this because the gem that you're trying to use has
been compiled for Ruby 1.8.x and these binaries are not compatible
with Ruby 1.9.x
I would recommend installation of the Development Kit as documented in
RubyInstaller wiki:
And when find a gem that does not work, for the installation as shown
in the DevKit instructions (gem install xxx --platform=ruby)
Please note that not all gems suffer this problem. The best to do is
contact the gem author and politely ask provide him a gem with
binaries for Ruby 1.9 too.
On Oct 15, 3:14 pm, "Srinivas P." <spavul...@gmail.com> wrote:
Hi Team,
I installed ruby 1.9.2, i am getting follwing error
This application has failed to start because msvcrt-ruby18.dll was not
found. Re-installing the application may fix this problem.
--
Luis Lavena
Actually I just did..
1. renamed Ruby to Ruby.old
2. Followed all the remaining instructions (with exception of the path
variables for ruby itself)
3. Ran ruby -v and gcc -v and both worked fine.
--
Posted via http://www.ruby-forum.com/.
Thanks Roger,
Can I ask one question though. If I have previously used the installer,
do I need to "uninstall" that version completely before installing the
ming/1.9 version?
Nope--you can have as many as you want on you system, just be aware that
"ruby gem installed commands" will use the first ruby they find in the
path, not necessarily the one they were installed with. So it's ok to
have multiple versions just realize that it will by default use the
first one in the path.
-=r
--
Posted via http://www.ruby-forum.com/\.
Hi Luis,
You're receiving this because the gem that you're trying to use has
been compiled for Ruby 1.8.x and these binaries are not compatible
with Ruby 1.9.x
I've followed your replies here and also on -core and you seem to be
very knowledgeable about Ruby. One thing I noticed about many (mostly
Windows) related questions from user was that they would happen to mix
different binary Ruby versions; accidentally.
Is there no mechanism for gems to depend on specific Ruby version and
arch-types for binaries (sometimes even sources) ?
thanks,
- Markus
On 16.10.2010 21:15, Luis Lavena wrote:
4. Copied Scite into the new Ruby folder.
5. Ran gem installs and everything is working fine thus far.
6. Tested a few programs...
So, I believe that if you have the one-click installer already installed
(the path variables are already set).
If you follow all the instructions located in the link and then do what
I listed it does work fine.
If there are any potential flaws with this, please let me know but so
far everything is working...
--
Posted via http://www.ruby-forum.com/.
The only issue I'm finding with upgrading is that some of the gem
binaries are built on another version so I get an error
msvcrt-ruby18.dll was not found. I know it's occurring because I have
msvcrt-ruby191.dll now and the gem was built with 18 instead of 191.
That's the only downfall so far.
What I don't understand is why don't the gem authors force a certain
"require ruby version" when installing their gems so that we know which
ones are 18 and which ones are 191...
Having to fish for which gems are which and then having to go to the
authors to find a new source is a bit frustrating.
--
Posted via http://www.ruby-forum.com/.
I've covered this case back in April 2009 on rubygems-devel list:
http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html
You can define a gem to be targeted at one version of Ruby (using gem
spec required_ruby_version attribute), however, you can't generate a
binary gem that target both 1.8.x and 1.9.x series of Ruby.
There are binary differences between 1.8.x and 1.9.x (different C-API,
different VM, etc) that made these pre-compiled extensions
incompatible.
Aaron Patterson came up with a nice idea called fat-binaries -- the
analogy to universal binaries of OSX -- which provides, under the same
gem binaries for both 1.8 and 1.9 versions of Ruby.
You can see examples of that in binary gems like sqlite3-ruby, mysql,
a series of DataMapper (DO) adapters and Nokogiri itself.
The above mentioned libraries rely on rake-compiler as helper to ease
both the binary gems generation and the fat-binary packaging.
But not all gem developers actually know about this and some of them
don't actually care about Windows binaries due it's complexities.
There are some gems that do not depend on external libraries (e.g.
rdiscount, RedCloth, BlueCloth and others) that only needs a compiler
to build its extension.
For those cases you can use RubyInstaller + DevKit and force the
platform during the gem installation:
gem install rdiscount --platform=ruby
That will trigger the compilation process and you're 100% sure, if it
succeed in the compilation, that the binaries are going to work with
your current version of Ruby.
You can read instructions on installation of these elements in our
wiki:
For the cases that depend on external libraries (mysql, sqlite3-ruby)
you will need to have available the same requirements for a Unix
system: headers and linking libraries available.
That means sometimes just indicate options during the gem
installation:
gem install mysql -- --with-mysql-include=C:/MySQL/include --with-
mysql-lib=C:/MySQL/lib/opt
And others steps required are more depending on the complexity of the
library you're installing.
But, is always better to politely ask the gem author to look into
these issues and also advise him to reach out RubyInstaller group for
assistance in providing these fat-binary gems.
On Oct 17, 6:00 am, Markus Fischer <mar...@fischer.name> wrote:
Hi Luis,
On 16.10.2010 21:15, Luis Lavena wrote:
> You're receiving this because the gem that you're trying to use has
> been compiled for Ruby 1.8.x and these binaries are not compatible
> with Ruby 1.9.xI've followed your replies here and also on -core and you seem to be
very knowledgeable about Ruby. One thing I noticed about many (mostly
Windows) related questions from user was that they would happen to mix
different binary Ruby versions; accidentally.Is there no mechanism for gems to depend on specific Ruby version and
arch-types for binaries (sometimes even sources) ?
--
Luis Lavena
One thing I definitely noticed like when I tried to install mysql I had
to do:
gem install mysql --platform=mswin32
and it worked fine..
With other files like ruby-opengl I had to go to the download page,
download the .gem file manually and install the gem locally and it
worked fine.
Testing apps and they all work fine.
Good information - this is exactly what I was looking for!
--
Posted via http://www.ruby-forum.com/.
J. D. wrote:
The only issue I'm finding with upgrading is that some of the gem
binaries are built on another version so I get an error
msvcrt-ruby18.dll was not found. I know it's occurring because I have
msvcrt-ruby191.dll now and the gem was built with 18 instead of 191.
yeah it's a concern being discussed by the rubygems fellas. For now
with 1.9 your only hope is basically to build "everything binary" from
scratch, which...works on and off.
-=r
--
Posted via http://www.ruby-forum.com/\.
The only issue I'm finding with upgrading is that some of the gem
binaries are built on another version so I get an error
msvcrt-ruby18.dll was not found. I know it's occurring because I have
msvcrt-ruby191.dll now and the gem was built with 18 instead of 191.
Yes, this is already exposed problem with RubyGems:
http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html
And suggestion to go with "Fat binaries" are a tempting option I'm
working on with original ideas form Aaron Patterson:
http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/
That's the only downfall so far.
What I don't understand is why don't the gem authors force a certain
"require ruby version" when installing their gems so that we know which
ones are 18 and which ones are 191...
Since RubyGems lack the ability to have 2 exact version number gems
(1.2.3) but targetting different Ruby versions (1.8.x, 1.9), renders
required_ruby_version kind of useless (as I pointed in RubyGems
mailing list).
Having to fish for which gems are which and then having to go to the
authors to find a new source is a bit frustrating.
Complain to the authors, or even better, patch and contribute the
changes.
Nothing else can be said since they are contributing for free with
their code for you to enjoy or be frustrated with.
On May 28, 11:30 am, "J. D." <jdezen...@gmail.com> wrote:
--
Luis Lavena
One thing I definitely noticed like when I tried to install mysql I had
to do:gem install mysql --platform=mswin32
and it worked fine..
http://blog.mmediasys.com/2008/08/10/rubygems-with-power-comes-responsibility/
With other files like ruby-opengl I had to go to the download page,
download the .gem file manually and install the gem locally and it
worked fine.
I believe that is a error in the published gem or how was published at
RubyForge. Please contact the gem developer/author and provide your
feedback.
On May 28, 10:16 am, "J. D." <jdezen...@gmail.com> wrote:
--
Luis Lavena
Roger Pack wrote:
J. D. wrote:
The only issue I'm finding with upgrading is that some of the gem
binaries are built on another version so I get an error
msvcrt-ruby18.dll was not found. I know it's occurring because I have
msvcrt-ruby191.dll now and the gem was built with 18 instead of 191.yeah it's a concern being discussed by the rubygems fellas. For now
with 1.9 your only hope is basically to build "everything binary" from
scratch, which...works on and off.
-=r
Well, I'm still new (only going into my second week of ruby). I've
already read 1 book but reading/doing are two different things.
Do you have a link or something to that extent that shows how to build a
binary gem from start to finish?
I learn fast but unfortunately with something like this (on a first time
try) I'd be fishing in the dark...
--
Posted via http://www.ruby-forum.com/\.
Being frustrated and complaining are really two different things. I
don't mind being frustrated and I usually will work through issues the
best way that I can. Once I'm up to par on Ruby and understand it much
better, I'd be happy to contribute. I'm the type of person that loves
contributing. Unfortunately, wanting to and knowing how to are also two
different things.
After upgrading to 1.9.1 one of the gems that I want to use is mysql.
When I require it, I receive the following message:
"The application has failed to start because msvcrt-ruby18.dll was not
found."
I know that is because I need to use msvcrt-ruby191.dll and that the gem
was built with another version.
So, how would I go (step by step) to trying to resolve the issues I'm
having with the mysql gem? Or, rather, what would you do step by step
to resolve the issue?
Many thanks in advance.
--
Posted via http://www.ruby-forum.com/.