From: Julian Leviston Date: 2005-08-12T20:24:45+09:00 Subject: 10.2.8 saga continued Hey guys, I just realised when I was "make"-ing the ruby 1.8.2, it kept saying "nothing to be done for All"... is that normal? Can anyone tell me if this is the normal results for a make? gcc -g -O2 -pipe -fno-common main.o dmyext.o libruby-static.a - ldl -lobjc -o miniruby compiling bigdecimal make[1]: Nothing to be done for `all'. compiling curses make[1]: Nothing to be done for `all'. compiling dbm make[1]: Nothing to be done for `all'. compiling digest make[1]: Nothing to be done for `all'. compiling digest/md5 make[1]: Nothing to be done for `all'. compiling digest/rmd160 make[1]: Nothing to be done for `all'. compiling digest/sha1 make[1]: Nothing to be done for `all'. compiling digest/sha2 make[1]: Nothing to be done for `all'. compiling dl compiling enumerator make[1]: Nothing to be done for `all'. compiling etc make[1]: Nothing to be done for `all'. compiling fcntl make[1]: Nothing to be done for `all'. compiling gdbm compiling iconv compiling io/wait make[1]: Nothing to be done for `all'. compiling nkf make[1]: Nothing to be done for `all'. compiling openssl make[1]: Nothing to be done for `all'. compiling pty make[1]: Nothing to be done for `all'. compiling racc/cparse make[1]: Nothing to be done for `all'. compiling readline make[1]: Nothing to be done for `all'. compiling sdbm make[1]: Nothing to be done for `all'. compiling socket make[1]: Nothing to be done for `all'. compiling stringio make[1]: Nothing to be done for `all'. compiling strscan make[1]: Nothing to be done for `all'. compiling syck make[1]: Nothing to be done for `all'. compiling syslog make[1]: Nothing to be done for `all'. compiling tcltklib compiling tk make[1]: Nothing to be done for `all'. compiling Win32API compiling win32ole compiling zlib make[1]: Nothing to be done for `all'. making ruby gcc -g -O2 -pipe -fno-common -L. main.o -lruby-static -ldl - lobjc -o ruby