On Wed, Aug 18, 2004 at 07:55:25PM +0100, Joe Orton wrote:
On Wed, Aug 18, 2004 at 10:54:13AM -0700, Stas Bekman wrote:
Joe Orton wrote: Thanks Joe.
Any chance this can be rewritten to find out what syntax to use (2.0 or 2.1) once and not do that repeatedly? This function is the cause of the slow configuration (too many shell calls), so trying to minimize it will be a great thing.
Why "repeatedly"? Surely since the value is cached it's only done twice, once for apr-config and once for apu-config?
No, I meant to have two branches: one for 2.0 and one for 2.1, so in case a call to the 2.0 style apxs returns no value it won't try to call 2.1 style?
Oh, well, I see what you mean if I add debugging in sub apxs. How can I
fix this if caching the values as $self->{...} doesn't already?
Writing Makefile for Apache::SubProcess apxs called for -q APU_CONFIG apxs called for -q EXTRA_CFLAGS apxs called for -q EXTRA_CPPFLAGS apxs called for -q EXTRA_CPPFLAGS Writing Makefile for Apache::SubRequest apxs called for -q APU_CONFIG apxs called for -q EXTRA_CFLAGS apxs called for -q EXTRA_CPPFLAGS apxs called for -q EXTRA_CPPFLAGS Writing Makefile for Apache::URI
I think that's because a new build config object is instantiated by each Makefile.PL, that's something that I'd like to see fixed, since it can be better than 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]
