Hi
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:
% ruby -v
ruby 1.7.3 (2002-12-19) [powerpc-darwin5.5]
% ruby setup.rb install
setup.rb: entering install phase…
—> packages
—> packages/runit-compat
—> lib
mkdir -p /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/
install rubyunit.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/
—> lib/runit
mkdir -p /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install assert.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install error.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install testcase.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install testresult.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install testsuite.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install testunit-installed
/Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
install topublic.rb /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit
—> lib/runit/cui
mkdir -p /Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit/cui
install testrunner.rb
/Users/jdf/ruby173/lib/ruby/site_ruby/1.7/runit/cui
<— lib/runit/cui
<— lib/runit
<— lib
<— packages/runit-compat
—> packages/testunit
—> lib
Loaded suite TS_TestUnit
Started
…
Failure!!!
test_suite(Test::Unit::TC_TestCase):
Should have had one test failure
…
install failed
hook
/Users/jdf/downloads/ruby/testunit-0.1.5/packages/testunit/lib/pre-install.rb
failed:
stack level too deep
try ‘ruby setup.rb --help’ for usage
···
–
Jim Freeze
Harris’s Lament:
All the good ones are taken.
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:
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
<:((><
···
Jim Freeze [mailto:jim@freeze.org] wrote:
RoleModel Software, Inc.
EQUIP VI
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:
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