I'd appreciate if you test that patch
I did another fresh install of the OS, re-installed Perl w/o the '-Duseshrplib' option, and built SSL/mod_perl/Apache (after applying your patch). Worked!
Now I wonder whether apply that patch for freebsd only or all.
does it work if you remove the -Wl,-E part?
Didn't work (this was with the earlier, shared Perl version).
OK, what if you take the original (with dynamic perl) and replace
-L/usr/local/lib/perl5/5.8.1/i386-freebsd/CORE -lperl
with
-Wl,-L/usr/local/lib/perl5/5.8.1/i386-freebsd/CORE -Wl,-lperl
I'm not familiar with FreeBSD linker so I'm just trying options from the ld manpage on FreeBSD: http://www.gsp.com/cgi-bin/man.cgi?section=1&topic=ld
What if you add -Wl,-i to the original command?
If the linker insists on resolving symbols, ideally what should be done is to link perl's libperl.so to mod_perl's libperl.a when the latter is created.
If I'm using the machine solely as a webserver (running mod_perl), does it matter if I build Perl statically or shared? If it doesn't matter (or if it's actually better for Perl to be static in this scenario), then I think I'm all set (using your patch). However, if the consensus is that I'd be better off with Perl built shared, then how do I "link perl's libperl.so to mod_perl's libperl.a"?
I'm not familiar with FreeBSD to give the right advice. I've CC'ed Vivek who may have one.
Meanwhile go ahead with the static perl build, and let's resolve the dynamic build while working against a special copy of perl (use -Dprefix as suggested before to have more than one perl build)
Thanks again for the help. (I plan to post a detailed build script once this is all done.)
;)
__________________________________________________________________ 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
