Re: Ruby c extensions on windows

On Jan 22, 3:29=A0pm, Nilbert Nullingsworth <[e-mail]>
wrote:
> Actually it is not the tools, it is my lack of knowledge on how to use
> them. First of all, it would never compile because it would find some
> reason not to, such as missing a header file (like winsock2.h, which
> Visual C++ is not missing, even though I set the compiler to look for
> includes in the VC++ include directory as well, even though winsock2.h
> doesn't even exist in that folder... So that's weird that VC++ can do
> it). Or it will be missing sys/time.h, even though it's not supposed
> to look for time.h in sys/. Then it can't find pcap.h even though it's
> in both the VC++ include directory which I have told the tools to
> search for include files, as well as in the same directory as the C++
> file, and the same directory from which the compiler was started from
> the command line. Visual C++ compiles it with no problem but that is
> because I have set up the program in the options to get the correct
> libs and include files and command line options, something which, even
> after multiple hours of searching with google. I do not know how to
> do. Along with several other errors like not being able to use nmake
> or rake or one of the other tools because openssl.so is messing up as
> the operating system cannot run %1 (what the blazes).
>

First, and again. Ruby is very picky about compilers and its version.

You should use exactly the same version of the compiler that was used
to create that Ruby binary.

If you're using either garbagecollect downloads or One-Click
Installer, then you need Visual C 6.0

That can't be sent, shared or adquired, since is 12 years old
compiler.

Please, again, try the above indicated instructions about getting
RubyInstaller and the Development Kit.

Once you have that setup, you can workout all the other details.

Help us help you, you actually don't provide the real information we
need. For example, you mention "It can find pcap.h which I have told
the tools to search for include files"

How you did that? We don't look for narrative text, we want facts and
screen output, actual error messages and environment variables.

> Pardon my outburst, I am severely frustrated because I have been at
> this constantly for about two days, and the multitude of travesties
> that have befallen me is very discouraging. I will look at that dev
> kit you suggested and be back for more help.


Is RubyInstaller AND the DevKit.

Also, when reporting issues, again, try to provide all the information
relevant to your environment:

Ruby version (ruby -v)
RubyGems environment info (gem env)
Your PATH (set PATH)
Your OS and configuration (which flavor of Windows, 32 or 64 bits,
etc.)

Complete output of the error you're receiving. If is long, use a paste
service like Pastie or Gist (GitHub) (if you have an account).

Also, if you can provide the sample script that generated the issue,
the better.

Again, help us help you.

--
Luis Lavena