Thanks. Yet, the web site and practical mod_perl book says that " "|Can't load DBI|" or *similar error for the IO module or whatever dynamic module mod_perl tries to pull in first*. The solution is to re-configure, re-build and re-install Perl and dynamic modules with the following flags when Configure asks for "|additional LD flags|"
Actually, DBI != DBD. I spoke too quickly...
I tested with a script without DBI but some other modules and it will give similar error for next module. I am not sure how net::mysql would help.
I'm afraid I haven't got a clue :(
Anyhow why not try to compile a perl in a separate location and try to compile mod_perl against that?
For example on some of our machines we have an RPM perl in /usr/bin/perl and a compiled one in /usr/local/bin/perl. It works quite well - you just need to make sure you use the right perl when you install modules - i.e. /usr/local/bin/perl -MCPAN -e 'install DBI'.
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
