Prev: DBI:ODBC on Vista: "could not load driver"
Next: ERROR: no driver for sqlite3 found (Ruby 1.9.0 + Windows
From: Marc Heiler on 22 Dec 2008 05:06
> Forget apt-get for Ruby. Maybe one day that will work as most people
> expect it should. But today is not that day.

I do not think it ever will. How many years have gone by now since the
first user had the problem with this concerning ruby on debian at least?
3 years?

Debian Users will continue to have split-up packages, and as a result
continue to have all these problems which reoccur every some months on
the list here, or on a forum somewhere else. This is a fundamental flaw
in philosophy concerning packaging on Linux boxes altogether in fact.

The only thing I do not quite understand is why debian developers do not
tell the users loudly that these problems are because of debian, and not
because of the ruby python etc... guys.
--
Posted via http://www.ruby-forum.com/.

From: Ezra Zygmuntowicz on 22 Dec 2008 12:06

On Dec 22, 2008, at 12:05 AM, James Britt wrote:

> Tom Cloyd wrote:
>> Greetings!
>> As an amateur, and intermittent, programmer, I often run right off
>> the edge of what I know. Sometimes this seems utterly needless.
>> Here's one such case:
>> In the past year I've switched from WindowsXP to Kubuntu Linux.
>> I've had to reload the operating system maybe four times, plus two
>> more due to acquiring a USB hard drive (now my primary drive), and
>> now setting my up Kubuntu to run from a flash drive. I have to
>> reinstall Ruby each time, of course. And....EACH TIME I RUN INTO
>> THE SAME STUPID PROBLEM, as exemplified by my experience yesterday:
>> I install Ruby 1.8 (yesterday, it was 1.8.7, of course) using
>> either apt-get or the Adept package manager. Then I install
>> Rubygems with apt-get (it's not in Adept's sources, apparently).
>> Ready to GO? You would think so. Naively, I always do. But it's not
>> to be. Now the madness starts, and this is what I want fixed.
>
>
> http://github.com/thewoolleyman/cinabox/tree/master/bootstrap_ruby.sh


If you use this script you should change line 27 to add the --disable-
pthreads flag

/configure --disable-pthreads

This can cause a 20-100% speed up on the interpreter as long as you
don't need to use tk.

Cheers-

Ezra Zygmuntowicz
ez(a)engineyard.com




From: Chad Woolley on 22 Dec 2008 15:42
On Mon, Dec 22, 2008 at 10:06 AM, Ezra Zygmuntowicz <ezmobius(a)gmail.com> wrote:
> If you use this script you should change line 27 to add the
> --disable-pthreads flag
>
> ./configure --disable-pthreads
>
> This can cause a 20-100% speed up on the interpreter as long as you
> don't need to use tk.

Thanks Ezra, committed:

http://github.com/thewoolleyman/cinabox/commit/a584281d510b03ff91261531f17a2247fe6e97df

I had incorrectly assumed this was the default...

-- Chad

From: Aníbal Rojas on 23 Dec 2008 07:58
Tom,

Yes, it is frustating, to make it a little bit simple install the
package: ruby-full which should give you everything that is ruby
related. But you will still need to install build-essential to be able
to compile native dependencies if you require them.

And yes, the differences between the Ruby community and the Debian
packagers always arise, and there are good points at both side about
how to do the things.

--
Aníbal Rojas
http://hasmanydevelopers.com
http://rubycorner.com
http://anibal.rojas.com.ve

On Dec 23, 1:15 am, Tom Cloyd <tomcl...(a)comcast.net> wrote:
> Greetings!
>
> As an amateur, and intermittent, programmer, I often run right off the
> edge of what I know. Sometimes this seems utterly needless. Here's one
> such case:
>
> In the past year I've switched from WindowsXP to Kubuntu Linux. I've had
> to reload the operating system maybe four times, plus two more due to
> acquiring a USB hard drive (now my primary drive), and now setting my up
> Kubuntu to run from a flash drive. I have to reinstall Ruby each time,
> of course. And....EACH TIME I RUN INTO THE SAME STUPID PROBLEM, as
> exemplified by my experience yesterday:
>
> I install Ruby 1.8 (yesterday, it was 1.8.7, of course) using either
> apt-get or the Adept package manager. Then I install Rubygems with
> apt-get (it's not in Adept's sources, apparently).
>
> Ready to GO? You would think so. Naively, I always do. But it's not to
> be. Now the madness starts, and this is what I want fixed.
>
> It turns out that Rubygems has a hidden dependency (I think I'm using
> the right term, but if not, correct me). It isn't automatically
> installed, and without it, gem installation simply crashes and burns,
> without useful comment. For an amateur such as me, this isn't helpful,
> to put it mildly. Here's what happens:
>
> ~$ sudo gem install RedCloth
> Building native extensions.  This could take a while...
> ERROR:  Error installing RedCloth:
>         ERROR: Failed to build gem native extension.
>
> /usr/bin/ruby1.8 extconf.rb install RedCloth
> extconf.rb:1:in `require': no such file to load -- mkmf (LoadError)
>         from extconf.rb:1
>
> Gem files will remain installed in /var/lib/gems/1.8/gems/RedCloth-4.1.1
> for inspection.
> Results logged to
> /var/lib/gems/1.8/gems/RedCloth-4.1.1/ext/redcloth_scan/gem_make.out
> ubuntu(a)ubuntu:~$
>
> The solution? Install the ruby1.8-dev library or package or whatever the
> heck it is. It's in the Adept package manager.
>
> I'm sure many on this list know all about this, but it's not reasonable
> to expect amateurs like to know such things, and there no sign on the
> side of the road advertising the fact. It's simply "secret knowledge". I
> hate secret knowledge.
>
> I've been "had" by this problem at least 6 times. It always happens
> about 5 weeks past the time I've forgotten about it. I DO have a full
> life aside from my Ruby adventures.
>
> So...if Rubygems needs this library or whatever, why cannot it check to
> see that it's present, and then complain if it's not? The error msg it
> does report means nothing to me at all. Personally, I think the Ruby
> package from Adept should include this, but that's another story.
>
> Basic idea: don't leave tiger traps lying about when you know that
> children will be coming down the path.
>
> Is this possible? Am I asking too much?
>
> (Update: the only reason by I ran into this problem at all was that I
> was reluctant to do on the flash drive OS what I do now regularly:
> compile and install from source. This is the best idea of all, of
> course, as documented recently by the fellow who issues the "Zen of
> Ruby" blog newsletter, since it produces an executable which is about
> twice as fast as that distributed by the package managers.)
>
> t.
>
> --
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
> Bellingham, Washington, U.S.A: (360) 920-1226
> << t...(a)tomcloyd.com >> (email)
> << TomCloyd.com >> (website)
> << sleightmind.wordpress.com >> (mental health weblog)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From: Jörg W Mittag on 23 Dec 2008 17:04
Marc Heiler wrote:
>> Forget apt-get for Ruby. Maybe one day that will work as most people
>> expect it should. But today is not that day.
> I do not think it ever will. How many years have gone by now since the
> first user had the problem with this concerning ruby on debian at least?
> 3 years?
>
> Debian Users will continue to have split-up packages, and as a result
> continue to have all these problems which reoccur every some months on
> the list here, or on a forum somewhere else. This is a fundamental flaw
> in philosophy concerning packaging on Linux boxes altogether in fact.

Can you explain how this is a fundamental flaw in Linux packaging?
TeX, Emacs, Perl, PHP, Python, Java, they all share most if not all of
Ruby's challenges: all have their own directory layouts, their own
search paths, their own library paths, their own versioning schemes,
their own package managers, their own distribution formats, multiple
different implementations, multiple different versions. Most have
native C extensions. Most were not created with Linux package managers
in mind -- heck, most were created before Linux package managers even
existed.

And yet, all of them work perfectly fine. All except Ruby.

This reminds me of the guy on the freeway listening to the traffic
channel and thinking to himself: "What are they talking about, a car
driving the wrong way on the freeway? It's not *a* car, it's hundreds
of them!"

jwm
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: DBI:ODBC on Vista: "could not load driver"
Next: ERROR: no driver for sqlite3 found (Ruby 1.9.0 + Windows