Scratch my previous e-mail. It seems that i did it accidentally under 1.8.6.
In 1.9.2 the building still fails:
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
ERROR:  Error installing win32-api:
ERROR: Failed to build gem native extension.

"C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/bin/ruby.exe" extconf.rb
checking for strncpy_s()... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

Provided configuration options:
--with-opt-dir
--without-opt-dir
 --with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
 --without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
 --srcdir=.
--curdir
--ruby=C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/bin/ruby
C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:368:in
`try_do': The complier failed to generate an executable file. (RuntimeError)
You have to install development tools first.
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:435:in
`try_link0'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:440:in
`try_link'
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:552:in
`try_func'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:797:in
`block in have_func'
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:693:in
`block in checking_for'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:280:in
`block (2 levels) in postpone'
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:254:in
`open'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:280:in
`block in postpone'
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:254:in
`open'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:276:in
`postpone'
 from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:692:in
`checking_for'
from C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/1.9.1/mkmf.rb:796:in
`have_func'
 from extconf.rb:9:in `<main>'


Gem files will remain installed in C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/gems/1.9.1/gems/win32-api-1.4.7
for inspection.
Results logged to C:/Documents and
Settings/xp/.pik/rubies/Ruby-192dev-preview3-1/lib/ruby/gems/1.9.1/gems/win32-api-1.4.7/ext/gem_make.out


I'm wondering how could it be that building native extensions worked under
1.8.6... i'd point out that my 1.9.2 is installed via pik install, but i
doubt that doing it with ruby installer would make any difference... i could
try of course...

Do you guys happen to have some Windows development tools installed by any
chance like Windows DDK, Visual Studio and such? No?

Jarmo

On Wed, Dec 15, 2010 at 11:30 PM, Jarmo <jarm...@gmail.com> wrote:

> Ok, it seemed that pik installed only legacy DevKit. I just created a fresh
> VM and installed DevKit like you guys did and succeeded to build win32-api.
> So, ruby does not need to be installed from the ruby installer, but works
> also with pik install, just FYI.
>
> Jarmo
>
>
> On Fri, Dec 3, 2010 at 5:58 AM, marekj <marekj....@gmail.com> wrote:
>
>> On Thu, Dec 2, 2010 at 2:15 PM, Alan Baird <aba...@bairdsnet.net> wrote:
>> > Actually, I think what I did was:
>> > 1) Install Ruby 1.9.2p0 from the one-click installer (not using pik)
>> > 2) Add that installation using: pik add c:\ruby\Ruby192\bin
>> > 3) Installed Watir
>> > 4) Installed the dev kit using; 'ruby dk.b init', then 'ruby dk.rb
>> install
>>
>> OK, I am with Alan on this one
>>
>> cd <DEVKIT_INSTALL_DIR>
>> ruby dk.rb init
>> ruby dk.rb review
>> ruby dk.rb install
>>
>> should set rubygems pre_install hook to ensure that --platform=ruby uses
>> devkit
>>
>>
>> > 5) ran what you saw in the first email
>> > Dunno if that will make a difference.
>> > Alan
>> > _______________________________________________
>> > Wtr-development mailing list
>> > Wtr-development@rubyforge.org
>> > http://rubyforge.org/mailman/listinfo/wtr-development
>> >
>> _______________________________________________
>> Wtr-development mailing list
>> Wtr-development@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/wtr-development
>>
>
>
_______________________________________________
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to