Comments on: Installing ruby 1.9preview1 on OS X Leopard

By: Mathieu Martin

Mathieu Martin — Mon, 23 Feb 2009 15:03:30 +0000

Readline is a library that can be used to easily implement a “memory” of past commands, among other features. It’s probably used by IRB.

By: roamy

roamy — Fri, 20 Feb 2009 04:34:02 +0000

I am just new at this
what is readline and why do i need it and what happens if i don’t have it

thanks fousto@me.com

By: Matthias Tarasiewic

Matthias Tarasiewic — Mon, 02 Feb 2009 14:54:37 +0000

does this actually still apply to ruby 1.9.1 stable? when i try to compile ruby with the –with-readline-dir=/usr/local switch, it says “configure: WARNING: unrecognized options: –with-readline-dir” other people seem to have that problem as well, see: http://www.ruby-forum.com/topic/175410

By: Matthias Tarasiewic

Matthias Tarasiewic — Mon, 02 Feb 2009 14:53:41 +0000

hi Mathieu, great posting. did you also try compiling the stable version 1.9.1 on leopard already? we are currently doing compiles for various osx versions, including leopard for the rubyosx (ruby one click installer for osx) project http://rubyosx.com the aim of the project is exactly what you said, keeping an osx version slim, not even installing xcode in the “worst case”. if you already did a compile, would you mind sending us your output of “ruby runner.rb” from the “/test” directory, so we could see which tests fail/work on your machine? see also the current thread on the rubyosx list regarding the osx leopard compile: http://rubyforge.org/pipermail/rubyosx-list/2009-February/000010.html

By: Alex

Alex — Mon, 22 Dec 2008 19:29:47 +0000

@Huki

Error: Port ruby1.9 not found

By: William

William — Fri, 05 Dec 2008 11:16:47 +0000

My apologies–it worked fine.Many thanks–the broken OS X readline has been a pain in my ass for years.Had to have someone hack the XBoard source to make it compile.

By: William

William — Fri, 05 Dec 2008 11:03:37 +0000

Thanks for posting patched readline source, but it didn’t work for me. Here’s what I got when I tried to make:

install: you may need to run ldconfig

By: BogoJoker » Helpful Configure Options For Development

BogoJoker » Helpful Configure Options For Development — Wed, 26 Nov 2008 06:37:59 +0000

[...] I wanted to easily reference both the Ruby 1.8 and Ruby 1.9 so I could easily work with both. I came across a neat switch that I had never cared to use before but made perfect sense for my [...]

By: Mathieu Martin

Mathieu Martin — Wed, 19 Nov 2008 16:41:55 +0000

@Hukl

I just noticed the last post on your site is about macports. I’ll have to check it out after work :-)

By: Mathieu Martin

Mathieu Martin — Wed, 19 Nov 2008 16:40:14 +0000

@Hukl

Funny, a few minutes ago I wanted to use wget and I don’t have it installed at the moment. I realized I wouldn’t mind using port for small things like that ;-)

I’d love a quick primer on how to deal with the Macport issues, actually.

The doc didn’t seem too clear to me last time I checked. I’d just like to know what clutter I can remove when an install fails, what file to update to fix a build and finally how to contribute that fix.

Are you aware of any good tutorial? OTOH I don’t want to spend an evening going through all of their doc ;-)

By: hukl

hukl — Wed, 19 Nov 2008 16:28:33 +0000

Sure, macports aren’t perfect but I like it more than having to maintain a lot of software that was built manually. I had it for years and it got messy. I can live with the macports issues and actually its not so hard to update a portfile for a new version. most of the time you have to adjust the url of the new tgz.

But I understand your reasoning.

By: Mathieu Martin

Mathieu Martin — Wed, 19 Nov 2008 15:58:44 +0000

@Hukl

LOL @ tada.wav :-)

I’m trying to minimize my use of Macports now. It’s actually not installed on my new machine.

On my previous machine, half the time when I used port, it would end up failing to build a dependency or something. I never found an obvious way to fix these problems and never really investigated further either. So the blame is probably half on my side.

What I like about building my own is that the day the next version comes out, I can go back and build it myself and not wait for the macport update. Also, by using the “industrial strength” approach described briefly in the article, I can actually have an arbitrary amount of rubies installed in parallel.

These reasons may seem a bit shallow, but I guess I just like to have a better understanding and complete control over how the stuff is installed on my machine. :-)

By: hukl

hukl — Wed, 19 Nov 2008 15:41:13 +0000

Why don’t you just use macports

$> port search ruby19 ruby19 lang/ruby19 1.9.1-preview1 Powerful and clean object-oriented scripting language

sudo port install ruby1.9

Tada.wav

By: Double Shot #335 « A Fresh Cup

Double Shot #335 « A Fresh Cup — Wed, 19 Nov 2008 11:58:04 +0000

[...] Installing ruby 1.9preview1 on OS X Leopard - How to do it. [...]