On Wed, Oct 13, 2004 at 05:02:30PM -0400, Stas Bekman wrote:
Joe Orton wrote:
If -lperl was specified on the link line and ldd does not show a dependency on libperl.so.N, then barring a complete linker fubar, it must be the case that a libperl.a was linked statically.
I doubt that this is the case, because I asked Martin to run nm on mod_perl.so and perl symbols were unresolved. Please see:
http://article.gmane.org/gmane.comp.apache.mod-perl/15266
Yes, I read the whole thread, this seems consistent with linking against
a bogus libperl.a on the system (maybe from a different version of Perl)
which doesn't define all the symbols which mod_perl needs. That seems far more likely than the linker being so borked it ignores -l flags.
Thanks Joe!
Martin, so may be you could try then finding all libperl.a occurences on your system, moving them to some hidden place (e.g. /tmp) and try to relink mod_perl.so as I've explained a few emails earlier... or upgrade the linker :)
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- 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
