I’ve searched ruby-talk for this topic, and the only messages I found show
the same symptoms I’m seeing: mod_ruby and eRuby compile fine, mod_ruby
runs (within Apache), but eRuby doesn’t. eRuby runs fine on the command
line, though.
I have a few more clues that may let someone figure out what may be wrong.
When the line
RubyRequire apache/eruby-run
is executed from httpd.conf, these error messages are written to the file
/var/log/httpd/error_log:
I’m mystified because mod_ruby seems to be running just fine. Those look
like libruby.a symbols, and if mod_ruby can see it why can’t eRuby?
Jim
···
–
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
“Hey, wait a minute. You’ve got both eyes! You’re no special agent.
You’re just some jerk who hates my moustache!” - The Tick
I’ve searched ruby-talk for this topic, and the only messages I
found show the same symptoms I’m seeing: mod_ruby and eRuby compile
fine, mod_ruby runs (within Apache), but eRuby doesn’t. eRuby runs
fine on the command line, though.
I have a few more clues that may let someone figure out what may be
wrong. When the line
RubyRequire apache/eruby-run
is executed from httpd.conf, these error messages are written to the
file /var/log/httpd/error_log:
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
If it’s supposed to link dynamically, it needs to be against libruby.dylib.
I hope that helps because I don’t have time to pursue it right now.
Why Darwin wants to call things ‘dylib’ when every other *nix calls them
'so’s is a mystery to me. The snipped error message is coming from the
dynamic linker, dyld, though, and that’s what it wants.
I’ve searched ruby-talk for this topic, and the only messages I
found show the same symptoms I’m seeing: mod_ruby and eRuby compile
fine, mod_ruby runs (within Apache), but eRuby doesn’t. eRuby runs
fine on the command line, though.
I have a few more clues that may let someone figure out what may be
wrong. When the line
RubyRequire apache/eruby-run
is executed from httpd.conf, these error messages are written to the
file /var/log/httpd/error_log:
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
–
I have suffered from being misunderstood, but I would have suffered a hell
of a lot more if I had been understood. -Clarence Darrow, lawyer and author
(1857-1938)
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
My mod_ruby is v0.9.6, and eruby is 0.9.7.
Jim
···
–
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
“You will notice that BeOS has taken the best parts from all the major
operating systems and made them its own. We’ve got the power of the Unix
command line, the ease of use of the Macintosh interface, and Minesweeper
from Windows.” – Tyler Riti
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
My mod_ruby is v0.9.6, and eruby is 0.9.7.
Please upgrade to mod_ruby 0.9.9 and the appropriate eRuby version:
there have been several OS X fixes, iirc. -sc
What is the rational for failure of “” << nil and of “” << :Foo ?
Apparently <<() (and +()) uses to_str() only, never to_s().
However this works: “#{nil}#{:Foo}”
I may do this to define to_str():
class NilClass
def to_str() to_s() end
end
class Symbol
def to_str() to_s() end
end
and then ("" << nil << :Foo) works.
… But I wonder if that could break things in some other cases?
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
My mod_ruby is v0.9.6, and eruby is 0.9.7.
Please upgrade to mod_ruby 0.9.9 and the appropriate eRuby version:
there have been several OS X fixes, iirc. -sc
That’s great news. I’ll do so.
Jim
···
–
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
“If you mark half [of this newsgroup’s] posts as read, you still get
basically all the same information, just with a bit less detail. [This] is
a holographic newsgroup.” – Tom “Tom” Harrington in rec.humor.oracle.d
Interesting… what version of mod_ruby/eRuby are you using? It
looks as though eRuby isn’t linking against ruby.so or libruby.(so|a).
I don’t have a copy of OS X around, but I think Shugo does. This
sound plausible? -sc
My mod_ruby is v0.9.6, and eruby is 0.9.7.
Please upgrade to mod_ruby 0.9.9 and the appropriate eRuby version:
there have been several OS X fixes, iirc. -sc
I tried that. Nothing changed: when I uncomment the lines
# # for Apache::ERubyRun
# RubyRequire apache/eruby-run
in httpd.conf, I see the same error messages spewed to the httpd error log
file.
–
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
“The Be staff…went to see the movie ‘Men in Black.’ …The movie makes
a point that is somehow appropriate – It is impossible to completely rid
the universe of bugs, but at least you can drive something fast, arm
yourself with powerful tools, and look good doing it.” – markg@be.com
What is the rational for failure of “” << nil and of “” << :Foo ?
Apparently <<() (and +()) uses to_str() only, never to_s().
However this works: “#{nil}#{:Foo}”
I may do this to define to_str():
class NilClass
def to_str() to_s() end
end
class Symbol
def to_str() to_s() end
end
and then (“” << nil << :Foo) works.
… But I wonder if that could break things in some other cases?
See whether http://www.ruby-talk.org/blade/11223, which was my shot
last year at explaining the #to_str/#to_s relation (both what and
why), is helpful. (It isn’t the last word in this area, but it’s
pretty much what I’d still say, so I’ll refer to it rather than quote
it at length
> > > Interesting... what version of mod_ruby/eRuby are you using?
> > > It looks as though eRuby isn't linking against ruby.so or
> > > libruby.(so|a). I don't have a copy of OS X around, but I
> > > think Shugo does. This sound plausible? -sc
> >
> > My mod_ruby is v0.9.6, and eruby is 0.9.7.
>
> Please upgrade to mod_ruby 0.9.9 and the appropriate eRuby
> version: there have been several OS X fixes, iirc. -sc
I tried that. Nothing changed: when I uncomment the lines
# # for Apache::ERubyRun
# RubyRequire apache/eruby-run
in httpd.conf, I see the same error messages spewed to the httpd
error log file.
Hmm... it looks like your httpd binary can't find any of the core ruby
symbols. Why that's happening I have no clue. Did you statically
compile in Ruby? -sc
See whether http://www.ruby-talk.org/blade/11223, which was my shot
last year at explaining the #to_str/#to_s relation (both what and
why), is helpful. (It isn’t the last word in this area, but it’s
pretty much what I’d still say, so I’ll refer to it rather than quote
it at length
Hmm… it looks like your httpd binary can’t find any of the core ruby
symbols. Why that’s happening I have no clue. Did you statically
compile in Ruby? -sc
As I wrote to you, I didn’t compile Apache, and I used the defaults for
eRuby.
See whether http://www.ruby-talk.org/blade/11223, which was my shot
last year at explaining the #to_str/#to_s relation (both what and
why), is helpful. (It isn’t the last word in this area, but it’s
pretty much what I’d still say, so I’ll refer to it rather than quote
it at length
Weird: for me, they both come up in English in Netscape but in
Japanese in lynx. I can’t quite puzzle through why, but thanks for
flagging the problem.