On Wed, Oct 13, 2004 at 08:26:43AM -0400, Stas Bekman wrote:
Joe Orton wrote:
This problem is probably caused by a bogus libperl.a on your system somewhere. What does:
ls -l /usr/lib/perl/5.6.1/CORE/libperl.* /usr/lib/libperl.* \ /usr/local/lib/libperl.*
give?
IMHO, it's libperl.so the linker is after, not libperl.a, since it's -rdynamic -lperl.
-rdynamic is an obsolete gcc alias for -Wl,--export-dynamic, and has no effect on whether the linker uses static or dynamically loaded libraries for -l options. (in fact it's completely redundant when linking a shared object like mod_perl as far as I'm aware)
We just use whatever flags perl gives us for linking (similar to apr-config ...).
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
-- __________________________________________________________________ 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
