Downloaded a fresh install of mingw today and got this: C:\downloads\latest\installer3>rake check (in C:/downloads/latest/installer3) "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i -c "make check" test succeeded ./miniruby.exe ../ruby_1_8/runruby.rb --extout=.ext -- "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test" --runner=console Loaded suite . Started .................................................................................................................................. .................................................................................................................................. ...................../ruby_1_8/test/openssl/test_hmac.rb:30: [BUG] Segmentation fault ruby 1.8.6 (2008-03-03) [i386-mingw32] This application has requested the Runtime to terminate it in an unusual way. Please contact the application''s support team for more information. Anybody seen that before? Thanks! -R
On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:> Downloaded a fresh install of mingw today and got this: > > C:\downloads\latest\installer3>rake check > (in C:/downloads/latest/installer3) > "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i > -c "make check" > test succeeded > ./miniruby.exe ../ruby_1_8/runruby.rb --extout=.ext -- > "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test" > --runner=console >Are you grabbing the sources from code.mmediasys.com or the github tarballs? The most up-to-date are the github tarballs, since didn''t had tiem to update the sync script for both svn repository and the zip package. In the dump site: http://dump.mmediasys.com/installer3/ You can see the text file (.txt) that contains the only errors during "rake check", of course excluding the test/readline/test_readline.rb file since it stall the whole procedure. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams
http://code.mmediasys.com/installer3/latest.zip On Tue, Jun 3, 2008 at 4:54 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote: >> Downloaded a fresh install of mingw today and got this: >> >> C:\downloads\latest\installer3>rake check >> (in C:/downloads/latest/installer3) >> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i >> -c "make check" >> test succeeded >> ./miniruby.exe ../ruby_1_8/runruby.rb --extout=.ext -- >> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test" >> --runner=console >> > > Are you grabbing the sources from code.mmediasys.com or the github tarballs? > > The most up-to-date are the github tarballs, since didn''t had tiem to > update the sync script for both svn repository and the zip package. > > In the dump site: > > http://dump.mmediasys.com/installer3/ > > You can see the text file (.txt) that contains the only errors during > "rake check", of course excluding the test/readline/test_readline.rb > file since it stall the whole procedure. > > -- > Luis Lavena > AREA 17 > - > Human beings, who are almost unique in having the ability to learn from > the experience of others, are also remarkable for their apparent > disinclination to do so. > Douglas Adams > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel >
if you get time, could I get a copy of the build that results in ''only a few'' errors as you mentioned, and outputs its errors here http://dump.mmediasys.com/installer3/ ? I wonder if it differs from mine somehow. Did it have openssl installed and run those tests, too? -R On Jun 3, 2008, at 4:54 PM, Luis Lavena wrote:> On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com> > wrote: >> Downloaded a fresh install of mingw today and got this: >> >> C:\downloads\latest\installer3>rake check >> (in C:/downloads/latest/installer3) >> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i >> -c "make check" >> test succeeded >> ./miniruby.exe ../ruby_1_8/runruby.rb --extout=.ext -- >> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test" >> --runner=console >> > > Are you grabbing the sources from code.mmediasys.com or the github > tarballs? > > The most up-to-date are the github tarballs, since didn''t had tiem to > update the sync script for both svn repository and the zip package. > > In the dump site: > > http://dump.mmediasys.com/installer3/ > > You can see the text file (.txt) that contains the only errors during > "rake check", of course excluding the test/readline/test_readline.rb > file since it stall the whole procedure. > > -- > Luis Lavena > AREA 17 > - > Human beings, who are almost unique in having the ability to learn > from > the experience of others, are also remarkable for their apparent > disinclination to do so. > Douglas Adams > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
On Wed, Jun 4, 2008 at 11:12 AM, Roger Pack <rogerpack2005 at gmail.com> wrote:> if you get time, could I get a copy of the build that results in ''only a > few'' errors > as you mentioned, and outputs its errors here > > http://dump.mmediasys.com/installer3/ > ? >http://dump.mmediasys.com/installer3/ruby-1.8.6-p114-i386-mingw32-2.txt What I needed to do was merge both ruby_mingw and rubygems_mingw since was splitted for MSI setup creation.> I wonder if it differs from mine somehow. > Did it have openssl installed and run those tests, too?I used the the same version of ruby I''m distributing to test, and actually the tests run on top of this version and not the installed one. (dunno if that''s clear, let me rephrase: tests uses the sandbox ruby version, not the one you used to build the sandbox). If test are failing that means something hacked your PATH because the test add the sandboxed ruby _before_ anything else, so if there is an openssl dll, will find it there first. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams
On Tue, Jun 3, 2008 at 5:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:> Downloaded a fresh install of mingw today and got this: > > C:\downloads\latest\installer3>rake check > (in C:/downloads/latest/installer3) > "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i > -c "make check" > test succeeded > ./miniruby.exe ../ruby_1_8/runruby.rb --extout=.ext -- > "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test" > --runner=console > > Loaded suite . > Started > .................................................................................................................................. > .................................................................................................................................. > ...................../ruby_1_8/test/openssl/test_hmac.rb:30: [BUG] > Segmentation fault > ruby 1.8.6 (2008-03-03) [i386-mingw32] > > > This application has requested the Runtime to terminate it in an unusual way. > Please contact the application''s support team for more information. > > > Anybody seen that before?Actually, I just remembered I have seen that before ;-). I was having the same problem a few months ago, which was caused by having another version of libeay32.dll and libssl32.dll in my system path. Luis helped me with it on this thread: http://rubyforge.org/pipermail/rubyinstaller-devel/2008-April/000277.html Hope that helps, Gordon
Probably could use a ''readme'' in there on how to set it up :) [like you need to add it to the path, then run the tests, and you need to merge the rubygems directory into the main to use gems]. I think what would be nice would be to have a package that includes the devkit. Maybe call it win32 power bundle or something, so that people can build things like mongrel, on the fly, if they want to. Then it could include those nice .cmd''s for gcc and make or what not. You might have to warn people that it will be using those instead of their cygwin versions, but power users won''t mind that. Ideally, you''d want it to be able to use the mingw versions whenever you are running a gem command, hence my suggesting that you bundle gems with gem_with_mingw_path.cmd # sets up the paths right for compilation Could also offer the ''normal'' OCI for mingw, too. GL! -R On Jun 4, 2008, at 9:47 AM, Luis Lavena wrote:> On Wed, Jun 4, 2008 at 11:12 AM, Roger Pack > <rogerpack2005 at gmail.com> wrote: >> if you get time, could I get a copy of the build that results in >> ''only a >> few'' errors >> as you mentioned, and outputs its errors here >> >> http://dump.mmediasys.com/installer3/ >> ? >> > > http://dump.mmediasys.com/installer3/ruby-1.8.6-p114-i386- > mingw32-2.txt > > What I needed to do was merge both ruby_mingw and rubygems_mingw since > was splitted for MSI setup creation. > >> I wonder if it differs from mine somehow. >> Did it have openssl installed and run those tests, too? > > I used the the same version of ruby I''m distributing to test, and > actually the tests run on top of this version and not the installed > one. > (dunno if that''s clear, let me rephrase: tests uses the sandbox ruby > version, not the one you used to build the sandbox). > > If test are failing that means something hacked your PATH because the > test add the sandboxed ruby _before_ anything else, so if there is an > openssl dll, will find it there first. > > -- > Luis Lavena > AREA 17 > - > Human beings, who are almost unique in having the ability to learn > from > the experience of others, are also remarkable for their apparent > disinclination to do so. > Douglas Adams > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
On Fri, Jun 6, 2008 at 12:41 AM, Roger Pack <rogerpack2005 at gmail.com> wrote:> Probably could use a ''readme'' in there on how to set it up :) [like you need > to add it to the path, then run the tests, and you need to merge the > rubygems directory into the main to use gems]. >There is a readme, there was a lot of discussion here and over ruby-talk about how to use it. To run the test it automatically add the sandboxed ruby in the path, you don''t need to do it manually. Also to run the tests there is no need to have rubygems into the sandboxed ruby.> I think what would be nice would be to have a package that includes the > devkit.There is, like I posted in my blog and several times over the mailing list, it''s available in the dump url: http://dump.mmediasys.com/installer3/ look for the sandbox-mingw-msys 7z package, is the latest version used to build that version of ruby.> Maybe call it win32 power bundle or something, so that people can build > things like mongrel, on the fly, if they want to. Then it could include > those nice .cmd''s for gcc and make or what not. You might have to warn > people that it will be using those instead of their cygwin versions, but > power users won''t mind that. Ideally, you''d want it to be able to use the > mingw versions whenever you are running a gem command, hence my suggesting > that you bundle gems with gem_with_mingw_path.cmd # sets up the paths right > for compilation >Don''t take this harsh but stop putting name to stuff and use it or create something. Again on the "gem_with_mingw" feel free to create whatever works for you, share with the community and get feedback, that''s the only way a theory can prove to be useful or totally useless. For me, the gcc, make and sh bat files make rubygems tests pass, also make mongrel and other gems painless to build without tweaking the path. You should keep in mind this is not a package for average joe ruby, this is a package for ruby developers/hackers and gem creators to provide feedback about MinGW compatibility. There are a lot of task that must be done before it can be massively used. Gordon generously took the time to collect and update the wiki with the Roadmap: http://rubyinstaller.rubyforge.org/wiki/wiki.pl?Roadmap Feel free to contribute on some of these task since most of them are priority.> > Could also offer the ''normal'' OCI for mingw, too.By normal you mean what? With this version of One-Click we are trying to avoid the mistakes did on the first place. I wouldn''t not invest time on something that in the long run will be dropped (like a NSIS or InnoSetup script) or cannot be easily manageable. Also the approach to bundle everything is not part of our goal right now. In any case only gems and extensions bundled in gems will be the only components that will be part of this, mainly because they have a mechanism to manage them, on the contrary of normal "setup.rb" extensions. There is a lot of discussion about RUBY_PLATFORM, changes between implementations and fixes for the underlying Ruby code to reduce the incompatibilities between platforms, so we have our hands busy right now, feel free to fork and contribute with your ideas and experiments, I''m eager to see what cool ideas can you bring to this project. Regards, -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams