From: Mark Wilson <mwilson13@...>
Date: 2002-12-21T09:32:10+09:00
Subject: Re: testunit-0.1.5 install failure (may be setup.rb)

I'm using Mac OS X 10.2.3 and Ruby 1.6.8 preview 4 (12-19-2002).  I get 
the following when I try to run 'sudo ruby setup.rb install':

setup.rb: entering install phase...
---> packages
---> packages/runit-compat
---> lib
mkdir -p /usr/local/lib/ruby/site_ruby/1.6/
install rubyunit.rb /usr/local/lib/ruby/site_ruby/1.6/
---> lib/runit
mkdir -p /usr/local/lib/ruby/site_ruby/1.6/runit
install assert.rb /usr/local/lib/ruby/site_ruby/1.6/runit
install error.rb /usr/local/lib/ruby/site_ruby/1.6/runit
install testcase.rb /usr/local/lib/ruby/site_ruby/1.6/runit
install testresult.rb /usr/local/lib/ruby/site_ruby/1.6/runit
install testsuite.rb /usr/local/lib/ruby/site_ruby/1.6/runit
install testunit-installed /usr/local/lib/ruby/site_ruby/1.6/runit
install topublic.rb /usr/local/lib/ruby/site_ruby/1.6/runit
---> lib/runit/cui
mkdir -p /usr/local/lib/ruby/site_ruby/1.6/runit/cui
install testrunner.rb /usr/local/lib/ruby/site_ruby/1.6/runit/cui
<--- lib/runit/cui
<--- lib/runit
<--- lib
<--- packages/runit-compat
---> packages/testunit
---> lib
Loaded suite TS_TestUnit
Started
Illegal instruction

How would I comment out running the tests and which files should be 
manually moved to which folders?  Thank you for a great program (I used 
the earlier version without incident with Ruby 1.6.7).

On Friday, December 20, 2002, at 07:19 PM, <nathaniel@NOSPAMtalbott.ws> 
wrote:

> Jim Freeze [mailto:jim@freeze.org] wrote:
>
>> I have installed on FreeBSD and Sun with no problems.
>> Since it works on the other OS's and it makes it
>> through config and setup, it may be a setup.rb problem.
>>
>> Installing on MacOSX (ruby 173) gives the following
>> error:
>
> <snip>
>
> Yes, it is a known issue that installing fails on OS X, and I have no
> earthly idea why (and no OS X box around on which to figure it out).
> It's dying when it tries to run the tests from within the install
> process, but if I remember correctly, running those exact same tests
> from the command line gives no problems. Perhaps you could investigate?
> ;-)
>
> It should work fine if you either (a) comment out running the tests, or
> (b) just copy the files over manually.
>
> I'd love to know what the stack looks like when it hits that "too deep"
> point.
>
>
> Nathaniel
>
> <:((><
> + - -
> | RoleModel Software, Inc.
> | EQUIP VI
>
>