Nobuyoshi Nakada wrote:
> Yes, obviously.  What I asked is what miniruby was about to do.

I think the very first invocation of miniruby during the compilation 
process is failling.

>> Is it committed in trunk?

The compilation still faisl with the bus error but as for miniruby -v:

Now, it is just looping away, eating CPU cycles :(

gcc -O -pipe -pipe -fno-common  -I. -I.ext/include/powerpc-darwin8.9.0 
-I../include -I..  -DRUBY_EXPORT  -c ../main.c
gcc -O -pipe -pipe -fno-common  -L.    main.o  libruby-static.a 
-lpthread -ldl -lobjc   -o miniruby
: -- stack frame ------------
0000 (0x128000): 00000000 <- lfp <- dfp
-- control frame ----------
c:0001 p:---- s:0001 b:-001 l:000000 d:000000 ------
---------------------------
[BUG] Bus Error
ruby 1.9.0 (2007-06-10) [powerpc-darwin8.9.0]

make: *** [.rbconfig.time] Abort trap
353 [10:50] roberto@robertotmp-al:yarv/build> ./miniruby -v
^D
^D

^C^C^C^C^Zload: 0.28  cmd: miniruby 27571 running 0.28u 3.49s
load: 0.28  cmd: miniruby 27571 running 0.39u 4.78s

^C^C^C^Z

I have to kill it in another window.  It is a plain 1.9 at changeset 
#12515.

> Thank you, I've investigated it, and will fix it.

As soon as I get a working ruby, I'll test it, thanks.


-- 
Posted via http://www.ruby-forum.com/.