From: Luis Lavena <luislavena@...>
Date: 2010-10-14T22:25:19+09:00
Subject: Re: Cannot install a gem on Windows x64

On Oct 13, 10:28 pm, Esen Sagynov <kadish...@gmail.com> wrote:
> Luis Lavena wrote in post #949880:
>
> > Something I noticed is that CUBRID libraries were compiled with newer
> > Visual C runtime libraries. That might have issues (or not, since
> > haven't installed it to test).
>
> For building CUBRID on Windows, Visual Studio 2008 is used. I am not
> sure about Ruby. I wonder how did you "noticed is that CUBRID libraries
> were compiled with newer Visual C runtime libraries"? How is it possible
> to notice?
>

http://www.cubrid.org/windows_downloads

Under "Software Requirements for CUBRID Manager": MS Visual C++ 2008
Redistributable Package

That is a hint that it depends on newer MSVCRT library (MSVCR80.DLL
actually)

> Luis Lavena wrote in post #949882:
>
> > You have CUBRID x64 installed. But Ruby is 32bits. That will not work.
> > You can't mix 32bits Ruby with 64bits libraries.
> > You need CUBRID 32bits libraries to compile against.
>
> If so, how users use MySQL x64 with Ruby? I heard many cases downloading
> third-party x64 compiled libmysql and successfully using it with Ruby.
> So how is that possible if Ruby SHOULD NEVER work with x64 compiled
> libraries? What about on Linux x64 with MySQL x64 and Ruby installed? It
> just does not make any sense to me.
>

Simple: you can install MySQL x64, but you need a 32bits libmysql.dll
in your Ruby\bin directory. That is what Ruby mysql extension uses and
then it can communicate with a local or remote 32/64 bits MySQL, that
is not a problem.

Now, if you need to build the extension (which is something you're
doing), then you need a 32bits MySQL to be able to compile against.

To our bad, Windows lack the concept of universal binaries that can
provide in the same DLL both 32 and 64 bits linking.

And I know is too much to say this but trust me, I kind of know what
is involved in this 32/64 bits and specially the MySQL subject.

--
Luis Lavena