Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Date: Fri, 18 Mar 2005 11:24:38 -0600 (CST)
From: Randy Kobes <randy@theoryx5.uwinnipeg.ca>
To: Stas Bekman <stas@stason.org>
cc: mod_perl Dev <dev@perl.apache.org>, doink123@abv.bg
Subject: Re: [mp2] finishing support for MP_USE_STATIC=1 MP_STATIC_EXTS=1
In-Reply-To: <423B046C.9080900@stason.org>
Message-ID: <Pine.LNX.4.56.0503181056170.12329@theoryx5.uwinnipeg.ca>
References: <423B046C.9080900@stason.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 18 Mar 2005, Stas Bekman wrote:

> When MP_STATIC_EXTS=1 is used all mp2 modules are statically linked with
> httpd, which is fine. However this leaves the APR-outside-of-mod_perl
> broken, since none of the objects available, and therefore all t/apr-ext
> tests fail.
>
> Should we just try to skip all those tests?
>
> Or should we nevertheless attempt to build shared objects to be used with
> APR.so?
>
> The only thing I'm not sure about is whether the latter
> approach will work, as it's possible that people use
> MP_STATIC_EXTS=1 because their perl doesn't support shared
> objects? But we still build APR.so.

Would building a static lib (Apache::Build::BUILD_APREXT),
as Win32 uses, be useful here?

-- 
best regards,
randy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org