Philippe M. Chiasson wrote:
Finally it breaks with:
LD_RUN_PATH="/usr/lib:/lib" cc -shared -L/usr/local/lib APR.o modperl_error.o modperl_bucket.o modperl_common_util.o modperl_common_log.o -L/usr/local/lib -o ../../../blib/arch/Apache2/auto/APR/APR.so -L/home/stas/apache.org/httpd-2.0/srclib/apr -lapr-0 -lrt -lm -lcrypt -lnsl -lpthread -ldl
/usr//bin/ld: cannot find -lapr-0
collect2: ld returned 1 exit status
I'm not sure how was this supposed to work in first place. Since libapr is not installed yet.
This is certainly a problem at the moment. I have been able to investigate a bit and I think I know
how to work around this problem cleanly.
There are currently 2 options I can think of.
The first one involves building mod_perl.a, building httpd and linking mod_perl.a, installing httpd
and then only resume the mod_perl build process.
That will be confusing. At least because one may need to 'su' in order to install things, so you can't make this transparent to the users. And they may want just to test the server, before installing it.
The other option I am currently investigating involves using libtool instead of cc to link the few
modules that must link directly against libapr.
How hard it is to do that?
-- __________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
