Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Date: Tue, 7 Dec 2004 01:11:25 -0500
From: Glenn Strauss <gs-lists-modperl@gluelogic.com>
To: dev@perl.apache.org
Subject: Re: [mp2] make test problems when configuring against source
Message-ID: <20041207061125.GB335@netspace.org>
References: <4189B26E.70902@stason.org> <41A50C0B.3010806@stason.org>
 <41ACEAFD.7000509@ectoplasm.org> <41ACEF10.5020206@stason.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41ACEF10.5020206@stason.org>
User-Agent: Mutt/1.4.1i

On Tue, Nov 30, 2004 at 05:07:12PM -0500, Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> [...]
> >>>Anybody remembers how were we dealing with that before? I don't think 
> >>>it has ever worked, besides when an explicit value of httpd was 
> >>>passed to t/TEST.
> >
> >
> >I think so too. I've managed to hack it up for the static build, with this
> >snipped of code:
> >
> >    my $httpd = File::Spec->catfile($build->{MP_AP_PREFIX}, 'httpd');
> >    $build->{'httpd'} = $httpd;
> >    push @Apache::TestMM::Argv, ('httpd' => $httpd);
> >
> >But it's only being applied to static builds, guess we could push it up
> >and apply it whenever MP_AP_PREFIX is a source dir.
> 
> How can we possibly do that w/o knowing whether httpd was built at that 
> location at all and whether it's the right one? I think we should abolish 
> any builds with MP_AP_PREFIX, but for the static build.
> 
> Wasn't it win32 where this was required? Randy, do we need the 
> build-against-httpd-source functionality on win32?
> 
> >>>Do we need to support the build against the source for any other 
> >>>reason than static build?
> >
> >
> >Exactly! As I was thinking about this, I also realized : Why on earth would
> >someone want to build against apache source if it wasn't for a static 
> >build.
> 
> For example if someone wants to build a module to be distributed elsewhere?
> 
> >>>In any case we should handle that case at A-T level and spit the 
> >>>right error message, like:
> >>>
> >>>------------
> >>>You have built mod_perl against httpd source, therefore it's not 
> >>>possible to run the test suite. You need to install first httpd if 
> >>>you haven't done so already. And run the test suite with:
> >>>
> >>> APACHE_TEST_HTTPD=/path/to/installed/bin/httpd make test
> >>>
> >>>or rebuild mod_perl using the MP_APXS argument (see the installation 
> >>>documentation for more details).
> >>>------------
> >
> >
> >How about at just making building against source deprecated of sorts 
> >with the
> >only exception left being the static build ?
> 
> Let's disable it for now (w/o cutting out the functionality) and see if 
> the patient screams or not.

I'm not sure I understand what is being disabled here.

What about system packagers?

I compile Apache 1.3 with MP1 as a DSO so that I can have a single
binary installation, but can run multiple instances of httpd with
different *.conf files, one with MP1 enabled (backend httpd) and
one without MP1 (frontend httpd)

Cheers,
Glenn

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