10.2.8 saga continued

J

Julian Leviston

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
 
R

Ralf Müller

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'.
Click to expand...

For compiling these ext-libs look at your ext/Setup file in the source
directory. You should remove the '#' sign for compiling.

best regards
ralf
 
J

Julian Leviston

Should they all be on?


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'.
Click to expand...

For compiling these ext-libs look at your ext/Setup file in the source
directory. You should remove the '#' sign for compiling.

best regards
ralf
Click to expand...
 
R

Ralf Müller

Should they all be on?
Click to expand...

this depends on what you want to do with ruby?

if unsure take them all. This will increase your interpreter from 1.3 MB to 2.5
MB. I'm sure many gems rely on some of these external libs. So it will you
keep painfree (hopefully) when installing additional ruby software.
 
J

Jason Foreman

Should they all be on?
=20
=20
Click to expand...

the ./configure script should turn on the ones appropriate for your
machine, depending on what headers it can find.

Since you're on 10.2.x, let me ask - Have you installed the BSD
subsystem? I don't remember if installing the Dev Tools will
automatically install that or not, and I remember it was not installed
by default.

It seems like during ./configure, none of the headers necessary for
building the Ruby extensions were found.

Untar a clean ruby tree again, run ./configure, and check the output.

Jason

On 12/08/2005, at 10:33 PM, Ralf M=FCller wrote:
=20
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'.
Click to expand...

For compiling these ext-libs look at your ext/Setup file in the source
directory. You should remove the '#' sign for compiling.

best regards
ralf
Click to expand...
=20
=20
Click to expand...
 
J

Julian Leviston

I want to run rubygems.

I want to run Rails.


this depends on what you want to do with ruby?

if unsure take them all. This will increase your interpreter from =20
1.3 MB to 2.5
MB. I'm sure many gems rely on some of these external libs. So it =20=
Click to expand...
 
J

Julian Leviston

That is about the most help ANYONE has been in ages. Thanks! This is =20
about the 10th time I've untarred a clean one, though...

Julian.

Should they all be on?
Click to expand...

the ./configure script should turn on the ones appropriate for your
machine, depending on what headers it can find.

Since you're on 10.2.x, let me ask - Have you installed the BSD
subsystem? I don't remember if installing the Dev Tools will
automatically install that or not, and I remember it was not installed
by default.

It seems like during ./configure, none of the headers necessary for
building the Ruby extensions were found.

Untar a clean ruby tree again, run ./configure, and check the output.

Jason


On Fri, 12 Aug 2005 20:24:45 +0900



Hey guys,

I just realised when I was "make"-ing the ruby 1.8.2, it kept =20
saying
"nothing to be done for All"... is that normal? Can anyone tell =20
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'.



For compiling these ext-libs look at your ext/Setup file in the =20
source
directory. You should remove the '#' sign for compiling.

best regards
ralf
Click to expand...
Click to expand...
Click to expand...
 
S

Steven Jenkins

Julian said:
That is about the most help ANYONE has been in ages. Thanks! This is
about the 10th time I've untarred a clean one, though...
Click to expand...

I don't know anything about MacOS, but I've seen cases where configure
was badly fooled by a problem running gcc or some lower-level script.
Configure sometimes concludes that a header or library is not present
because an attempt to locate it fails. This conclusion can be wrong if
the reason for the failure is something other than absence of the header
or library. Look at config.log and see if there's some repeated failure.

Steve
 
R

Ralf Müller

I want to run rubygems.

I want to run Rails.
Click to expand...

Maybe you've already done this, but:

rubygems:
try "ruby setup.rb" inside the rubygems directory. try "which ruby" order "type
ruby" (bash specific). The output should be the ruby, you've hopefully installed
with the ext-libs.

rails:
"gem install rails"

you should perform all these actions under the same user, you've installed ruby
with.

hth

best regards
ralf
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Readline extension doesn't compile with ruby-1.8.4 on RedHat 7.3 0
There has been an error while running make. Halting theinstallation. 0
[1.9/trunk] Bus error / abort trop with latest sources 5
Building ruby on Solaris (without root permissions). 4
Again, Zlib load error on HP-UX 4
Making 1.9.0 on Mac OS 10.4 1
Cross Compiling Ruby external modules for the Nokia 770. 0
Sparc and Alpha build fails 1

Members online

Total: 59 (members: 1, guests: 58)
Robots: 394

Forum statistics

Threads
473,969
Messages
2,570,161
Members
46,705
Latest member
Stefkari24

Latest Threads

Top