Stas Bekman wrote:
Geoffrey Young wrote:

hi all

the docs say MP_APXS may go away, but I recall some discussion to the contrary. has the status of MP_APXS changed?


do they? I think it's quite the opposite now and I have updated the docs. I guess I've missed some places, please tell me where.

I was looking at


http://perl.apache.org/docs/2.0/user/install/install.html#MP_APXS


Now that Randy has added APXS for win32, we don't need MP_AP_PREFIX for the DSO build. Though we will need it for the static build, so both are here to stay.

ok



[EMAIL PROTECTED] Apache-IncludeHook]$ perl Makefile.PL -apxs /apache/2.1/worker/perl-5.8.1/bin/apxs
...

>


[EMAIL PROTECTED] Apache-IncludeHook]$ make
...
cc -c  -I/apache/2.0/worker/perl-5.8.1/include

^^^
why is it 2.0? and not 2.1?

that's the problem I'm addressing


Are you sure that /apache/2.1/worker/perl-5.8.1/bin/apxs doesn't' have 2.0 paths in it?

yup. I take lots of steps to make sure there is no overlap in any of my builds - each variant gets a clean copy of httpd-2.0 to work with and everything is truncated nightly.


I don't understand the problem clearly, MP::MM::WM is using A::BuildConfig to get its data, so it's already aware of the command line args, no?

that's just it, WM doesn't seem to be picking up data parsed via Apache::TestMM::filter_args(). but even if it did, the only data in Apache::BuildConfig is from the mod_perl I installed last (which is the 2.0 install you see in -I above).


what I was thinking about doing was instead of BuildConfig doing

sub new {
    bless( {
                 'MODPERL_PRIVLIBEXP' => '/perl/perl-5.8.1/lib/5.8.1',


it could do


sub new {
    bless( '/apache/2.1/worker/perl-5.8.1/' => {
                 'MODPERL_PRIVLIBEXP' => '/perl/perl-5.8.1/lib/5.8.1',
...
           '/apache/2.0/worker/perl-5.8.1/' => {
                 'MODPERL_PRIVLIBEXP' => '/perl/perl-5.8.1/lib/5.8.1',

instead. the issue is, though, what to use as the key. my thought was to truncate either MP_APXS or MP_AP_PREFIX to the apache install root and use that as the key. or maybe 'default' as the key the first time, and subsequent installs get versioned or something.

is the problem still unclear? I can try to illustrate it better if need be.

--Geoff




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to