| 1 |
I wanted mod_perl on my gentoo system. It seems to be touchy about |
| 2 |
thread safety. Well that seemed reasonable, but it failed to emerge |
| 3 |
(gentoo-speak for "install from source"), and left me without my |
| 4 |
favorite editor (!!!): vim. |
| 5 |
|
| 6 |
To handle thread-safety issues, I put this in /etc/package.use: |
| 7 |
> # perl needs threads for mod_perl to work (or else mod_perl can't have threads) |
| 8 |
> # Moreover vim cannot be built unless perl and libperl have the same use flags |
| 9 |
> dev-lang/perl ithreads -ldap perlsuid doc |
| 10 |
> sys-devel/libperl ithreads -ldap perlsuid doc |
| 11 |
> www-apache/mod_perl ithreads -ldap doc |
| 12 |
|
| 13 |
The result was failure. I was not rebuilding vim, but it got killed |
| 14 |
in the process anyway: it errors out on startup. |
| 15 |
Moreover, I cannot re-emerge vim either, because it fails in about the |
| 16 |
same way as mod_perl. |
| 17 |
Both perl and libperl seem to build okay with the above lines in package-use. |
| 18 |
My running kernel matches /usr/src/linux, so the headers should be good. |
| 19 |
I'm looking for guidance from anyone who's using mod_perl with apache. |
| 20 |
Here's the build log: |
| 21 |
|
| 22 |
treat portage # cat /var/tmp/portage/www-apache/mod_perl-2.0.4-r1/temp/build.log |
| 23 |
>>> Unpacking source... |
| 24 |
>>> Unpacking mod_perl-2.0.4.tar.gz to /var/tmp/portage/www-apache/mod_perl-2.0.4-r1/work |
| 25 |
* Applying mod_perl-2.0.1-sneak-tmpdir.patch ... [ ok ] |
| 26 |
* Applying CVE-2009-0796.patch ... [ ok ] |
| 27 |
>>> Source unpacked in /var/tmp/portage/www-apache/mod_perl-2.0.4-r1/work |
| 28 |
>>> Compiling source in /var/tmp/portage/www-apache/mod_perl-2.0.4-r1/work/mod_perl-2.0.4 ... |
| 29 |
Errno architecture (i686-linux-2.6.24-gentoo-r4-kosmanor) does not |
| 30 |
match executable architecture |
| 31 |
(i686-linux-thread-multi-2.6.28-gentoo-r5-kosmanor) at |
| 32 |
/usr/lib/perl5/site_perl/5.8.8/Errno.pm line 11. |
| 33 |
Compilation failed in require at /usr/lib/perl5/5.8.8/File/Path.pm line 185. |
| 34 |
BEGIN failed--compilation aborted at /usr/lib/perl5/5.8.8/File/Path.pm line 185. |
| 35 |
Compilation failed in require at Apache-Test/lib/Apache/TestConfig.pm line 46. |
| 36 |
BEGIN failed--compilation aborted at |
| 37 |
Apache-Test/lib/Apache/TestConfig.pm line 46. |
| 38 |
Compilation failed in require at lib/ModPerl/Code.pm line 27. |
| 39 |
BEGIN failed--compilation aborted at lib/ModPerl/Code.pm line 27. |
| 40 |
Compilation failed in require at lib/Apache2/Build.pm line 48. |
| 41 |
BEGIN failed--compilation aborted at lib/Apache2/Build.pm line 48. |
| 42 |
Compilation failed in require at Makefile.PL line 36. |
| 43 |
BEGIN failed--compilation aborted at Makefile.PL line 36. |
| 44 |
* |
| 45 |
* ERROR: www-apache/mod_perl-2.0.4-r1 failed. |
| 46 |
* Call stack: |
| 47 |
* ebuild.sh, line 49: Called src_compile |
| 48 |
* environment, line 2677: Called die |
| 49 |
* The specific snippet of code: |
| 50 |
* perl Makefile.PL PREFIX="${D}"/usr MP_TRACE=1 MP_DEBUG=1 |
| 51 |
MP_USE_DSO=1 MP_APXS=${APXS} INSTALLDIRS=vendor < /dev/null || die; |
| 52 |
* The die message: |
| 53 |
* (no error message) |
| 54 |
* |
| 55 |
* If you need support, post the topmost build error, and the call |
| 56 |
stack if relevant. |
| 57 |
* A complete build log is located at |
| 58 |
'/var/tmp/portage/www-apache/mod_perl-2.0.4-r1/temp/build.log'. |
| 59 |
* The ebuild environment file is located at |
| 60 |
'/var/tmp/portage/www-apache/mod_perl-2.0.4-r1/temp/environment'. |
| 61 |
* |
| 62 |
|
| 63 |
-- |
| 64 |
Kevin O'Gorman, PhD |
Archives