[#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-18 00:46:29 UTC
List: ruby-core #3763
Hello.

In message "Re: Windows build problems (1.8.2preview3)"
    on Nov.17,2004 23:24:02, <nathaniel@talbott.ws> wrote:
| Sorry if I wasn't clear, but that's what I did. Actually, I've found 
| that just running "nmake" twice in a row will cause the problem, too. I 
| did find a weird fix, though: if I delete one of the obj files, like 
| ruby.obj, and then run nmake, it will rebuild miniruby correctly (after 
| rebuilding the obj file) and works fine from then on (i.e. I can 'nmake 
| test' and 'nmake install' without problems).

OK, I (maybe) understand the situation.

But, I could not reproduce this problem...
I used VC++5, VC++6 and VC++7.1, but all OK.


| If you need more info, please let me know, and thanks for your help!

Please tell us your nmake version.
And, If you can, please tell me how did you create your
compilation environment.


For example, my nmake version is:
Microsoft(R) Program Maintenance Utility Version 7.10.3077

And my compilation environment (VC7.1) is normal installation
of Micrsoft Visual Studio .NET 2003 (Japanese).

Regards,
-- 
U.Nakamura <usa@garbagecollect.jp>



In This Thread

Prev Next