Matz, thank you for releasing 1.8.4!!
i was wondering if i can manually update the windows one-click-installer
to
1.8.4
if anyone knows how, that would be great, if not, i’ll wait for that
release…
merry christmas!
Dirk.
Dirk M. wrote…
Matz, thank you for releasing 1.8.4!!
Let me second (or whatever it’s up to) that. Thanks for allowing the
Syck
patch, too.
i was wondering if i can manually update the windows one-click-installer
to
1.8.4
if anyone knows how, that would be great, if not, i’ll wait for that
release…
There will be a release some time in the next couple of weeks (thanks
for
your work on that, Mr. Curt H.), but you can certainly run 1.8.4 on
Windows before that. If you want to compile Ruby, to play nice with the
One-Click Installer you might need to use the same compiler (VS7 IIRC).
Alternatively, you can get the Ruby-mswin32 build from
Index of /ruby/mswin32/en - “1.8.4” will probably be
up
shortly, and even if it isn’t, I’m pretty sure the Dec.23 version of
1.8.4-preview3 is identical.
Happy Christmas!
Dave
Dave B. wrote:
Alternatively, you can get the Ruby-mswin32 build from
Index of /ruby/mswin32/en - “1.8.4” will probably be
up
shortly, and even if it isn’t, I’m pretty sure the Dec.23 version of
1.8.4-preview3 is identical.
Has anyone else tried to build this with MSVC Version 14? At first, I
got:
.\miniruby.exe ./win32/mkexports.rb -output=msvcr80-ruby18.def
msvcr80-ruby18-static.lib
./win32/mkexports.rb:6:in `foreach’: Bad file descriptor (Errno::EBADF)
from ./win32/mkexports.rb:6
NMAKE : fatal error U1077: ‘.\miniruby.exe’ : return code ‘0x1’
Stop.
After debugging, it appeared that _WIN32_WCE should be changed to _WIN32
at line 143 of win32.h and numerous places in win32.c. That gives me a
working miniruby.exe, but I can’t make any further progress in nmake: I
get
C:\Ruby184>nmake
Microsoft (R) Program Maintenance Utility Version 8.00.50727.39
Copyright (C) Microsoft Corporation. All rights reserved.
compiling Win32API
NMAKE : fatal error U1077: ‘.\miniruby.exe’ : return code ‘0x1’
Stop.
You need to use a snapshot after 2006/01/01. I am working on the steps
that will be necessary.
-austin
Eric C. wrote:
Dave B. wrote:
Alternatively, you can get the Ruby-mswin32 build from
Index of /ruby/mswin32/en - “1.8.4” will probably be
up
shortly, and even if it isn’t, I’m pretty sure the Dec.23 version of
1.8.4-preview3 is identical.Has anyone else tried to build this with MSVC Version 14? At first, I
got:.\miniruby.exe ./win32/mkexports.rb -output=msvcr80-ruby18.defmsvcr80-ruby18-static.lib
./win32/mkexports.rb:6:in `foreach’: Bad file descriptor (Errno::EBADF)
from ./win32/mkexports.rb:6
NMAKE : fatal error U1077: ‘.\miniruby.exe’ : return code ‘0x1’
Stop.After debugging, it appeared that _WIN32_WCE should be changed to _WIN32
at line 143 of win32.h and numerous places in win32.c. That gives me a
working miniruby.exe, but I can’t make any further progress in nmake: I
getC:\Ruby184>nmake
Microsoft (R) Program Maintenance Utility Version 8.00.50727.39
Copyright (C) Microsoft Corporation. All rights reserved.compiling Win32API
NMAKE : fatal error U1077: ‘.\miniruby.exe’ : return code ‘0x1’
Stop.
I also get an error at that line in that file:
.\miniruby.exe ./win32/mkexports.rb -output=msvcr80-ruby18.def
msvcr80-ruby18-static.lib
./win32/mkexports.rb:6: [BUG] Segmentation fault
ruby 1.8.4 (2005-12-24) [i386-mswin32]
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application’s support team for more information.
This was using the .NET 2.0 nmake utility.
Eric C. wrote:
C:\Ruby184>nmake
Microsoft ® Program Maintenance Utility Version 8.00.50727.39
Copyright © Microsoft Corporation. All rights reserved.compiling Win32API
NMAKE : fatal error U1077: ‘.\miniruby.exe’ : return code ‘0x1’
Stop.
I managed to compile the latest stable snapshot this way:
set MAKE=nmake
nmake
There seems to be an issue with backslashes and miniruby. If you don’t
set MAKE, miniruby is called with something like
–make=“c:\Programme\VS8\VC\bin\nmake.exe”, and the backslashes get lost
somehow.
- Günter
Austin Z. wrote:
You need to use a snapshot after 2006/01/01. I am working on the steps
that will be necessary.-austin
Is a stable 1.8.4 compilable on Windows yet?
On 6/17/06, Kris L. [email protected] wrote:
Austin Z. wrote:
You need to use a snapshot after 2006/01/01. I am working on the steps
that will be necessary.
Is a stable 1.8.4 compilable on Windows yet?
Yes, but you don’t want to. It’s not Ruby itself. I will be talking
to some developers from Microsoft later this week, I hope, to see what
can be done toward the overall problem.
-austin
Austin Z. wrote:
On 6/17/06, Kris L. [email protected] wrote:
Austin Z. wrote:
You need to use a snapshot after 2006/01/01. I am working on the steps
that will be necessary.
Is a stable 1.8.4 compilable on Windows yet?Yes, but you don’t want to. It’s not Ruby itself. I will be talking
to some developers from Microsoft later this week, I hope, to see what
can be done toward the overall problem.-austin
I’m having the same problem mentioned compiling the newest release of
ruby (1.8.5-p12). I’m trying to compile it with VS2005 under WinXP SP2,
VS2005 SP1. Running configure.bat from the VS2005 Command Prompt works
fine, but after running nmake, I get the following error:
.\miniruby.exe C:/ruby-src2/ruby-1.8.5-p12/win32/mkexports.rb
-output=ms
vcr80-ruby18.def msvcr80-ruby18-static.lib
C:/ruby-src2/ruby-1.8.5-p12/win32/mkexports.rb:6: [BUG] Segmentation
fault
ruby 1.8.5 (2006-12-25) [i386-mswin32_80]
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application’s support team for more information.
lib -nologo -machine:x86 -out:msvcr80-ruby18.lib
-def:msvcr80-ruby18.def
LIB : fatal error LNK1104: cannot open file ‘msvcr80-ruby18.def’
NMAKE : fatal error U1077: ‘“C:\Program Files\Microsoft Visual Studio
8\VC\BIN\l
ib.EXE”’ : return code ‘0x450’
Stop.
The reason I’m needing to compile ruby is because I’ll be compiling a
dll with VS2005 using SWIG, to be imported into a ruby app. Any help
would be much appreciated.
Thanks,
Amir