[#3726] Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...>

Hi --

15 messages 2004/11/12
[#3749] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3751] Re: Fixnum#clone and Float#clone raise different exceptions — Yukihiro Matsumoto <matz@...> 2004/11/16

Hi,

[#3752] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3785] The latest 1.8.2 cvs prints parse error when starting extension compiling — Yukihiro Matsumoto <matz@...>

Hi,

13 messages 2004/11/23
[#3787] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling — Johan Holmberg <holmberg@...> 2004/11/23

Re: Windows build problems (1.8.2preview3)

From: "U.Nakamura" <usa@...>
Date: 2004-11-17 03:48:08 UTC
List: ruby-core #3759
Hello,

In message "Windows build problems (1.8.2preview3)"
    on Nov.17,2004 10:39:32, <nathaniel@talbott.ws> wrote:
| Anyhow, I start with the usual "win32\configure.bat" followed by 
| "nmake". Everything seems to work fine at this point, although I do get 
| the following warning at one point:

This warning is meaningless. You can simply ignore it.


| At this point, I seem to have a working ruby (and miniruby) - manually 
| running "miniruby rubytest.rb" outputs "test succeeded" as it should. 
| However, if I run "nmake test", I get the following output:
(snip)
| And my miniruby disappears! I'm guessing ruby is actually OK, but it's 
| still causing me a bit of concern. Any ideas?

On my environment, "nmake test" says:

./rubytest.rb:3:in `load': No such file to load -- ./rbconfig.rb (LoadError)
        from ./rubytest.rb:3

I think these are make target confusion problem.

IMHO, you should run "nmake test" only after "nmake", just like
win32/README.win32 says :)
Of course, I'm trying to solve this problem.


Thank you.
-- 
U.Nakamura <usa@garbagecollect.jp>




In This Thread