As of apache-2.0.52-r3 and -1.3.33-r1 apache uses new configuration paths and locations. mod_ruby currently has paths and locations hardcoded into it's ebuild. The ebuild needs a new revision that uses apache-module.eclass so it doesn't break when we unmask the new apache revisions. Thanks!
Ping to Ruby people. Any progress? This is blocking apache updates. Thanks.
I'm playing around with it now, but I'm a little unsure all that has to be done with it.
Committed 1.2.4-r1 which is my attempt to be compliant.
I emerged mod_ruby-1.2.4-r1 yesterday on a system with the new Apache 2.0.53 and noticed some things: 1) The 20_mod_ruby.conf files has a wrong LoadModule directive, it searches for mod_ruby in extramodules/mod_ruby.so, the new Apache needs modules/mod_ruby.so since now all modules are in the /usr/lib/apache2/modules/ folder, extramodules/ folder is deprecated. 2) I don't have an Apache1 to test that, but in the new ebuild the line APACHE1_MOD_CONF="/mod_ruby" seems wrong to me, if you want to use files/mod_ruby.conf then you have a / there that shouldn't be there... 3) After I manually fixed the LoadModule path and started my Apache2 with -D RUBY I got these errors in my error_log: [Thu Mar 24 20:59:39 2005] [error] mod_ruby: failed to require apache/ruby-run [Thu Mar 24 20:59:39 2005] [error] mod_ruby: error in ruby [Thu Mar 24 20:59:39 2005] [error] mod_ruby: ruby:0:in `require': No such file to load -- apache/ruby-run (LoadError) The same goes for apache/eruby-run if I uncomment the eruby code in the 20_mod_ruby.conf file. But I have both ruby and eruby installed... What I noticed is that the emerge of mod_ruby-1.2.4-r1 removed the /usr/lib/ruby/1.8/apache/ directory, where previously ruby-run and eruby-run were located, what can I do to have these again?
please see http://home.xnull.de/misc/mod_ruby.patch this ebuilds works for me except that mod_ruby causes segfaults on 2.0
I can confirm that Benedikt Boehm's ebuild works indeed very well and compiles fine and installs all the needed files, now Apache2 + mod_ruby starts well and doesn't complain. Though I'm also getting segfaults on Apache2, whenever I look at a page with mod_ruby loaded into Apache2 it segfaults. :(
*** Bug 88928 has been marked as a duplicate of this bug. ***
Just committed 1.2.4-r2, let's see if that fixes the problems.
I have the same problem as mentioned in comment #6 and unfortunately 1.2.4-r2 doesn't seem to help.
It seems LFS is the culprit here - mod_ruby works fine with an APR built without LFS support. Not sure as to the solution yet, but since LFS-capable APR results in segfault parties for both mod_ruby and mod_perl LFS support will likely be removed (and soon !).
Created attachment 56615 [details, diff] patch to mod_ruby_1.2.4-r2.ebuild This patch fixes the segfault problem in apache2 It forces "-D_FILE_OFFSET_BITS=64" into your cflags when using apache2 Might not be the most 'correct' way, but it works I would think the real fix should be in apxs2 (net-www/apache), which should include this define in the `apxs2 -q CFLAGS` output
Created attachment 56643 [details, diff] patch to correctly use apxs2 in configure.rb I believe i've found the correct way to get the cflags. Apxs2 is poorly documented, but it appears that there is an EXTRA_CFLAGS field that is now used for apache2. (see apache's bug #29771). The patch modifies the configure script to check for these values, if using apxs2.
I tried mod_ruby-1.2.4-r2 with David Parrott's last patch (Comment #12, the configure.rb patch) and it compiled fine and works on Apache 2.0.53 without problems, I get no more segfaults when accessing pages and all works fine so far! :) Thanks for the patch David!
Patch from comment #12 doesn't work for me. The child processes still segfault. Is there anything else I can do or try?
Correction: Patch from comment 12 does work for me. Thanks, David.
*** Bug 96062 has been marked as a duplicate of this bug. ***
Obsolete bug, FIXED.
