Ruby

=begin
ruby --version
ruby 1.9.1 (2008-10-28 revision 19983) [i386-mswin32]
=end

=begin
Is a common problem not just of 1.9.1 release but previous (1.8.5, 1.8.6 and 1.8.7).

None of these files are included, even the bindings has been built for them.

Even worse, zlib has been updated and renamed to zlib1, which add another question of the version used to build the distribution.

I believe one of the reasons is license distribution, but I could be wrong.

=end

=begin
I moved these DLL-s from the Ruby 1.8 bin folder.

The following other DLL-s are also required to use gems.

*  libeay32.dll

However ZLIB still fails to initialise.

-- Ergo: we can not use gems with this 1.9.1 preview.

w.
=end

=begin
Thanks Luis

That was a great tip. A possible work around to get the gems to update was

A. Copy

    ZLIB1.DLL  as -->  ruby-1.9.1-preview1-i386-mswin32\bin\ZLIB.DLL

B. And Copy

*  SLEAY32.DLL
*  libeay32.dll
*  readline.dll

From the ruby 1.8 bin folder.

This isn't really a reliable fix. It just demonstrates where the solution lies. There are about 5 ohter libraries in the 1.8 that dont' get moved into the 1.9 preview.

I think that aspect is OK, and stil - The readme could tell us what the correct versions to use and wehre to find them. Please?

Cheers,
Will

=end

=begin
That's one of my complains about the bianries uploaded at garbage collect.

You need to do a lot of undocumented monkey patching to get you started.

Even worse, you need to figure out, by trial and error, which version of OpenSSL, readline and zlib was used to build the binaries and distribute with those, since the wrong dll will make it fail.

I've asked in the past for some documentation/build script that details the packages used without luck

We had to live with this on current One-Click Installer. Another of the reasons for the new MinGW-based installer.

=end

=begin
On Sat, Jan 10, 2009 at 10:23 AM, Luis Lavena [email protected] wrote:

Even worse, zlib has been updated and renamed to zlib1, which add another question of the version used to build the distribution.

I believe one of the reasons is license distribution, but I could be wrong.

zlib1.dll is the correct name for the DLL, according to what I recall
of the zlib pages. However, that's intended for a "system" compile
(e.g., made with msvc6 compatibility only); if a win32 distro is made
that need to ship a zlib DLL, it needs to have a different name (e.g.,
ruby-zlib.dll) so that there's no chance of Ruby conflicting with the
"system" zlib DLL.

-austin¶

Austin Ziegler * [email protected] * http://www.halostatue.ca/
* [email protected] * http://www.halostatue.ca/feed/
* [email protected]

=end

=begin
On Sat, Jan 10, 2009 at 4:33 PM, Austin Ziegler [email protected] wrote:

On Sat, Jan 10, 2009 at 10:23 AM, Luis Lavena [email protected] wrote:

Even worse, zlib has been updated and renamed to zlib1, which add another question of the version used to build the distribution.

I believe one of the reasons is license distribution, but I could be wrong.

zlib1.dll is the correct name for the DLL, according to what I recall
of the zlib pages. However, that's intended for a "system" compile
(e.g., made with msvc6 compatibility only); if a win32 distro is made
that need to ship a zlib DLL, it needs to have a different name (e.g.,
ruby-zlib.dll) so that there's no chance of Ruby conflicting with the
"system" zlib DLL.

Thank you Austin for the info.

However, is not that the lib is named zlib1 or could be ruby-zlib, the
problem is the lack of the binary in the "binary" distribution.

--
Luis Lavena
AREA 17¶

Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

=end

=begin
Please cross-reference to GEM bug:

[#23515] gem install not working with ... ruby-1.9.1-preview1-i386-mswin32

I'll repeat the lazy work-around hack that I used:

Take the following DLL-s from the working 1.8 installation:

*  ZLIB1.DLL  as -->  ruby-1.9.1-preview1-i386-mswin32\bin\ZLIB.DLL

And Copy

*  SLEAY32.DLL
*  libeay32.dll
*  readline.dll

Again, if the preview can't be mad to include appropriate DLL-s, then at least instructions on how to acquire them ought to be included in the read-me. After all there's a good chance that there could be incompatibilities between the DLL versions from v1.8 and the new release.

w.
=end

=begin
I do not think it's the license. At least both sleay32 and zlib have are very liberal and can be distributed in source and binary form.

André
=end

=begin
Hi guys, I wrote a post to share my experience on fixing the problem. Basically what you need is downloading those dlls from their homepage and copy to ruby path.

http://blog.orangecabin.com/2009/05/install-ruby-1-9-on-windows-using-zip-binary/
=end

=begin
I know it is a hack but that it works for me.
=end

=begin
On Sat, May 30, 2009 at 9:02 AM, Pan Li [email protected] wrote:

Issue #999 has been updated by Pan Li.

Hi guys, I wrote a post to share my experience on fixing the problem. Basically what you need is downloading those dlls from their homepage and copy to ruby path.

http://blog.orangecabin.com/2009/05/install-ruby-1-9-on-windows-using-zip-binary/

There are install instructions already for those packages.

http://www.garbagecollect.jp/ruby/mswin32/en/documents/install.html

Too bad ruby-lang is linking directly to the files and not to
garbagecollect website.

--
Luis Lavena
AREA 17¶

Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

=end