Ruby 1.9 compilation - question

Ruby
1

I’m following the instructions at -
http://amerj.info/2009/03/19/howto-install-rails-23-and-ruby-19-on-ubuntu-for-mysql-and-sqlite3/

I don’t know if I’m having a critical problem or not. Here’s the
abbreviated CLI output:

…ruby-1.9.1-p243$ ./configure --prefix=/usr/local
–with-openssl-dir=/usr --with-readline-dir=/usr
–with-zlib-dir=/usr

configure: WARNING: unrecognized options: --with-openssl-dir,
–with-readline-dir, --with-zlib-dir
.
.
.
creating config.h
configure: creating ./config.status
config.status: creating Makefile
configure: WARNING: unrecognized options: --with-openssl-dir,
–with-readline-dir, --with-zlib-dir
tomc@tomc-desktop:~/software_archive/ruby-1.9.1/ruby-1.9.1-p243$

I look at “info configure”, but what I got with that didn’t look helpful
(not to me, anyway).

Can someone advise me as to what this means, and what I need to do
different, if anything?

Thanks very much,

t.

–

Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
2

<< PLEASE DISREGARD the request for help below. >>

This 1.9 install royally messed up by 1.8.7 install, among other things.
I’ve abandoned it completely. Don’t have time for this nonsense.
Ah…but getting 1.8.7 working again was a nightmare in itself. Ruby 1.9
just won’t disappear. Arrrrgh! Sad.

Back to normal now, though. Sigh.

t.

Tom C. wrote:

–with-zlib-dir=/usr
–with-readline-dir, --with-zlib-dir
t.

$ ruby19 -ropenssl -rzlib -rreadline -e “puts ‘Happy new Ruby’”
Happy new Ruby

This looks rather confirming. Does it means my install is A-OK?

t.

–

Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
3

This 1.9 install royally messed up by 1.8.7 install, among other things.
I’ve abandoned it completely. Don’t have time for this nonsense.

One strategy - out of possibly many - is to use versioned directories,
similar to how GoboLinux http://gobolinux.org/ does it. Then installs
like the one you mentioned have no chance to “mess” up anything at all.

Ah…but getting 1.8.7 working again was a nightmare in itself. Ruby 1.9
just won’t disappear. Arrrrgh! Sad.

If you stick to solutions like the FHS, then the one to blame is not
ruby,
but FHS - or you, in this case. People who are not afraid to compile
from
source should not complain too loudly if their solution is crappy. :wink:

On Gobolinux (or more generally AppDir strategy) all one does would be

rm -rf /Programs/Ruby/1.9.1

and gone it is (ok, on Gobolinux you need to remove the symlinks, but
this can be tied to an event-listener, so the above is still valid).

Most other strategies (such as using a package manager)
are less elegant than the above ideal of versioned “app dirs”.
(But I do admit that there might be a few other problems, with the
biggest one possibly that not many people will use this setup, because
the FHS is ubiquitous and won’t disappear. Personally however, I use it
since 5 years at least for ruby, and it works nicely.)

4

Marc H. wrote:

This 1.9 install royally messed up by 1.8.7 install, among other things.
I’ve abandoned it completely. Don’t have time for this nonsense.

One strategy - out of possibly many - is to use versioned directories,
similar to how GoboLinux http://gobolinux.org/ does it. Then installs
like the one you mentioned have no chance to “mess” up anything at all.

Yeah. Have looked a bit at this, before. Makes so much sense. I now
(today) moving toward getting a test install up and running. Life should
be easy(er). This traditional nix file system is simple insane. Why
don’t people fix the problem? (Well, obvious some of them have…)

Ah…but getting 1.8.7 working again was a nightmare in itself. Ruby 1.9
just won’t disappear. Arrrrgh! Sad.

I basically blew the whole day yesterday, working on this problem, only
to end up back where I started.

If you stick to solutions like the FHS, then the one to blame is not
ruby,
but FHS - or you, in this case. People who are not afraid to compile
from
source should not complain too loudly if their solution is crappy. :wink:

Ouch. (long silence…)

On Gobolinux (or more generally AppDir strategy) all one does would be

rm -rf /Programs/Ruby/1.9.1

and gone it is (ok, on Gobolinux you need to remove the symlinks, but
this can be tied to an event-listener, so the above is still valid).

“event-listener” - please explain, if you have time. I roughly
understand the concept, but could you name one which might be used, say
on gobolinux?

Most other strategies (such as using a package manager)
are less elegant than the above ideal of versioned “app dirs”.
(But I do admit that there might be a few other problems, with the
biggest one possibly that not many people will use this setup, because
the FHS is ubiquitous and won’t disappear. Personally however, I use it
since 5 years at least for ruby, and it works nicely.)

“It” being gobolinux?

Thanks for your thoughts!

Tom

–

Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)
5

Tom C. wrote:

tomc@tomc-desktop:~/software_archive/ruby-1.9.1/ruby-1.9.1-p243$

$ ruby19 -ropenssl -rzlib -rreadline -e “puts ‘Happy new Ruby’”
Happy new Ruby

This looks rather confirming. Does it means my install is A-OK?

t.

–

Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)