"SB" == Stas Bekman <[EMAIL PROTECTED]> writes:
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"?
SB> I'm not familiar with FreeBSD to give the right advice. I've CC'ed SB> Vivek who may have one.
I build mine dynamic, just because it is easier.
I use the freebsd ports to build apache+modssl, then I build mod_perl from CVS. It all just works[tm].
Vivek, could you please try building the way Bryn had and see if it's an issue with having an old gcc or something that we really need to handle in mp1? In case you don't have the whole thread, it started here:
http://marc.theaimsgroup.com/?l=apache-modperl&m=106668950807617&w=2
we now have a workaround for the the build against the static perl
http://marc.theaimsgroup.com/?l=apache-modperl&m=106671628526322&w=2
but then Bryn rebuilt his perl dynamically, and again hit the same problem:
http://marc.theaimsgroup.com/?l=apache-modperl&m=106672332431690&w=2
he also reported that adding -Wl,-i to the failing command solves the problem with dynamic perl (-i postpones the resolving of the symbols to the run-time).
I'd rather have someone running on FreeBSD and familiar with linkers polish these patches out, rather then me unfamiliar and not running FreeBSD trying to guess how things should be ;) Thanks Vivek.
__________________________________________________________________ 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
