Embperl and Apache 2

[BitTwiddler]

Hi,

I am currently using apache 1.3 with Embperl and I am in the process of migrating to Apache 2 since Apache 1.3 is being dropped from the portage. I emerge Embperl on my test system and it worked fine. Unfortunately when I started Apache I got the following error.

Cannot load /usr/lib/apache2/modules/mod_embperl.so into server: /usr/lib/apache2/modules/mod_embperl.so: undefined symbol: PL_dowarn

Now considering that the current version of Embperl in the portage is a release candidate and is almost 2 years old I can see this happening. I am just wondering if anybody has plans to include some of the latest versions of Embperl in the portage. Is there anything I can do to help make this happen ? I would really appreciate it.

Best regards,

BT

[BitTwiddler]

Hi,

After my original post I tried a few things to resolve my problem. My first attempt was to create a local entry for Embperl Version 2.1.0. That worked and the package built properly and installed. Unfortunately I still got the same error message when Apache tried to load the module. I also tried building Embperl without portage to see if it was one of the default settings in the portage build that was causing the problem. The results where that I got the same error. I then tried emerging mod_perl, which after some alterations to the use flags for perl (-ithreads) built and installed with no errors. When I tried to load Apache I got the following error.

Cannot load /usr/lib/apache2/modules/mod_perl.so into server: /usr/lib/apache2/modules/mod_perl.so: undefined symbol: Perl_Ipatchlevel_ptr

And ideas or help would be appreciated.

Thanks

[BitTwiddler]

Hello everyone,

Well I got embedded Perl to work. Turns out the solution was to enable ithreads for perl and libperl. When I did this and rebuilt both Perl packages, Modperl and then Embperl everything worked. The following changes were made to /etc/portage/package.use.

dev-lang/perl ithreads
sys-devel/libperl ithreads

Also instead of using the 2.0-RC4 version of embperl, I created a local entry for 2.0.1. The ebuild file is the same as the 2.0-RC but just renamed to reflect 2.0.1.

I did have one minor problem after the changes. Vi would not work. The solution was to emerge vi again. And just in case I ran revdep-rebuild to catch any other dependencies failures. Which it did not detect any problems.

Hope this helps

BT