You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2004/11/04 05:39:10 UTC
[mp2] make test problems when configuring against source
As several users have reported to the list, when one configures against
the httpd-2.0 source .e.g:
perl Makefile.PL MP_INST_APACHE2=1
MP_AP_PREFIX=/home/stas/apache.org/httpd-2.0
'make test' fails with:
something is wrong, mod_perl 2.0 build should have supplied all the needed
information to run the tests. Please post lib/Apache/BuildConfig.pm along
with the bug report at
/home/stas/apache.org/mp2-cvs/Apache-Test/lib/Apache/TestConfig.pm line 349.
+--------------------------------------------------------+
| Please file a bug report: http://perl.apache.org/bugs/ |
+--------------------------------------------------------+
A-T rightfully fails since it doesn't know where apxs/httpd are (they were
never supplied).
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.
Do we need to support the build against the source for any other reason
than static build?
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).
------------
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
>> 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.
Of course the build should be updated *not* to ask for the location of the
Apache source, but of httpd/apxs instead.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
Glenn Strauss wrote:
> 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.
we are talking about 'make test' here. In any case nothing was disabled at
the end.
> 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)
And you should be able to do the same with mp2. Let us know if you have a
problem, Glenn.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Glenn Strauss <gs...@gluelogic.com>.
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
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Randy Kobes wrote:
>
>> I think whatever is best for Unix would be fine for Win32.
>> Win32 installations are pretty standard, so specifying one
>> of MP_AP_PREFIX (the top-level installed directory) or the
>> path to the installed Apache.exe (or the path to an
>> installed apxs, if it exists) would allow us to find all the
>> path information needed to build and run the tests.
>
>
> Thanks Randy.
>
> I will try to keep MP_AP_PREFIX intact and see if we can get away with it.
So all I did is inserting a prompt for MP_APXS before asking for the httpd
source:
http://svn.apache.org/viewcvs?view=rev&rev=109383
Randy, if this new prompt is totally irrelevant to win32, please add the
appropriate logic to the conditional so this step won't be run.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> I think whatever is best for Unix would be fine for Win32.
> Win32 installations are pretty standard, so specifying one
> of MP_AP_PREFIX (the top-level installed directory) or the
> path to the installed Apache.exe (or the path to an
> installed apxs, if it exists) would allow us to find all the
> path information needed to build and run the tests.
Thanks Randy.
I will try to keep MP_AP_PREFIX intact and see if we can get away with it.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Tue, 30 Nov 2004, Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> > Stas Bekman wrote:
> >
> >> Randy Kobes wrote:
> >>
> >>> [...]
> >>> Is the thinking though to drop MP_AP_PREFIX? Win32 could use
> >>> the location of (an installed) apxs instead, if available,
> >>> but at present we don't assume apxs is present. Or one could
> >>> use the location of the installed Apache.exe - that would
> >>> probably be better.
> >>
> >> We are discussing to drop only for DSO. The static build will still
> >> use MP_AP_PREFIX.
> >>
> >> btw, what win32 sources are you talking about? httpd source?
Yes, I had in mind building against the httpd-2.0 sources.
At present this wasn't designed to work on Win32 -
MP_AP_PREFIX is assumed to be the top-level Apache2
installation directory. And as I mentioned earlier, I
think there's little motivation (in the Win32 world) to
change things so that it would build against the httpd-2.0
sources.
If MP_AP_PREFIX is enabled only for static builds, then
we'd have to find some variant to use for Win32. Or,
perhaps, if there's not too much branching, keep the
present meaning of MP_AP_PREFIX for Win32?
> >> An alternative solution is not to disable the DSO build
> >> against MP_AP_PREFIX, but die on 'make test' if it's
> >> attempted w/o specifying apxs and of course changing
> >> the perl Makefile.PL to ask for the apxs/httpd instead
> >> of the source.
> >
> > This solution sounds like a good one to me so far. Keeping MP_AP_PREFIX
> > is acceptable, it's just that instead of meaning "either an apache
> > installation
> > tree or an apache source", we'd make it an apache installation path
> > _unless_
> > it's a static build.
>
> Well, that's not exactly what I was suggesting. Let's no
> redefine the meaning of MP_AP_PREFIX on the fly, besides
> 'apache-installation-path' doesn't exist on most
> prepackaged distros, since things are spread around the
> system. I was talking to keep things as they are but
> refuse 'make test' w/o httpd passed and not ask for
> MP_AP_PREFIX if no args are passed to Makefile.PL, or ask
> for it, if the user has failed to path httpd/apxs values.
I think whatever is best for Unix would be fine for Win32.
Win32 installations are pretty standard, so specifying one
of MP_AP_PREFIX (the top-level installed directory) or the
path to the installed Apache.exe (or the path to an
installed apxs, if it exists) would allow us to find all the
path information needed to build and run the tests.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> Randy Kobes wrote:
>>
>>> [...]
>>>
>>> Is the thinking though to drop MP_AP_PREFIX? Win32 could use
>>> the location of (an installed) apxs instead, if available,
>>> but at present we don't assume apxs is present. Or one could
>>> use the location of the installed Apache.exe - that would
>>> probably be better.
>>
>>
>> We are discussing to drop only for DSO. The static build will still
>> use MP_AP_PREFIX.
>>
>> btw, what win32 sources are you talking about? httpd source?
>>
>> An alternative solution is not to disable the DSO build against
>> MP_AP_PREFIX, but die on 'make test' if it's attempted w/o specifying
>> apxs and of course changing the perl Makefile.PL to ask for the
>> apxs/httpd instead of the source.
>
>
> This solution sounds like a good one to me so far. Keeping MP_AP_PREFIX
> is acceptable, it's just that instead of meaning "either an apache
> installation
> tree or an apache source", we'd make it an apache installation path
> _unless_
> it's a static build.
Well, that's not exactly what I was suggesting. Let's no redefine the
meaning of MP_AP_PREFIX on the fly, besides 'apache-installation-path'
doesn't exist on most prepackaged distros, since things are spread around
the system. I was talking to keep things as they are but refuse 'make
test' w/o httpd passed and not ask for MP_AP_PREFIX if no args are passed
to Makefile.PL, or ask for it, if the user has failed to path httpd/apxs
values.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Randy Kobes wrote:
>
>> [...]
>>
>>Is the thinking though to drop MP_AP_PREFIX? Win32 could use
>>the location of (an installed) apxs instead, if available,
>>but at present we don't assume apxs is present. Or one could
>>use the location of the installed Apache.exe - that would
>>probably be better.
>
> We are discussing to drop only for DSO. The static build will still use
> MP_AP_PREFIX.
>
> btw, what win32 sources are you talking about? httpd source?
>
> An alternative solution is not to disable the DSO build against
> MP_AP_PREFIX, but die on 'make test' if it's attempted w/o specifying apxs
> and of course changing the perl Makefile.PL to ask for the apxs/httpd
> instead of the source.
This solution sounds like a good one to me so far. Keeping MP_AP_PREFIX
is acceptable, it's just that instead of meaning "either an apache installation
tree or an apache source", we'd make it an apache installation path _unless_
it's a static build.
> That's probably the best solution.
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
>>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?
>
>
> At present Win32 does use MP_AP_PREFIX for the location of
> the installed Apache2, and things such as the includes and
> lib directories are determined from it (and rely on the
> standard installation layout under MP_AP_PREFIX). It would
> take more work to get it to work with a Win32 source
> directory, but that's probably not worth it, as few users
> would use it, and plus, the Win32 sources have their own
> layout of where things lie (for mp1, it got to be quite
> intricate allowing both an installed and source apache
> tree).
>
> Is the thinking though to drop MP_AP_PREFIX? Win32 could use
> the location of (an installed) apxs instead, if available,
> but at present we don't assume apxs is present. Or one could
> use the location of the installed Apache.exe - that would
> probably be better.
We are discussing to drop only for DSO. The static build will still use
MP_AP_PREFIX.
btw, what win32 sources are you talking about? httpd source?
An alternative solution is not to disable the DSO build against
MP_AP_PREFIX, but die on 'make test' if it's attempted w/o specifying apxs
and of course changing the perl Makefile.PL to ask for the apxs/httpd
instead of the source.
That's probably the best solution.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Tue, 30 Nov 2004, 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?
At present Win32 does use MP_AP_PREFIX for the location of
the installed Apache2, and things such as the includes and
lib directories are determined from it (and rely on the
standard installation layout under MP_AP_PREFIX). It would
take more work to get it to work with a Win32 source
directory, but that's probably not worth it, as few users
would use it, and plus, the Win32 sources have their own
layout of where things lie (for mp1, it got to be quite
intricate allowing both an installed and source apache
tree).
Is the thinking though to drop MP_AP_PREFIX? Win32 could use
the location of (an installed) apxs instead, if available,
but at present we don't assume apxs is present. Or one could
use the location of the installed Apache.exe - that would
probably be better.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
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.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [mp2] make test problems when configuring against source
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> please followup on this issue asap, as this is critical for mp2.0 release.
Every time I take a vacation, things seem to just pile up ;-)
> Stas Bekman wrote:
>
>>As several users have reported to the list, when one configures against
>>the httpd-2.0 source .e.g:
>>
>>perl Makefile.PL MP_INST_APACHE2=1
>>MP_AP_PREFIX=/home/stas/apache.org/httpd-2.0
>>
>>'make test' fails with:
>>
>>something is wrong, mod_perl 2.0 build should have supplied all the
>>needed information to run the tests. Please post
>>lib/Apache/BuildConfig.pm along with the bug report at
>>/home/stas/apache.org/mp2-cvs/Apache-Test/lib/Apache/TestConfig.pm line
>>349.
>>+--------------------------------------------------------+
>>| Please file a bug report: http://perl.apache.org/bugs/ |
>>+--------------------------------------------------------+
>>
>>A-T rightfully fails since it doesn't know where apxs/httpd are (they
>>were never supplied).
This is a problem incredibly similar to what happens during the static
build process.
>>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.
>>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.
>>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 ?
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
Re: [mp2] make test problems when configuring against source
Posted by Stas Bekman <st...@stason.org>.
please followup on this issue asap, as this is critical for mp2.0 release.
Stas Bekman wrote:
> As several users have reported to the list, when one configures against
> the httpd-2.0 source .e.g:
>
> perl Makefile.PL MP_INST_APACHE2=1
> MP_AP_PREFIX=/home/stas/apache.org/httpd-2.0
>
> 'make test' fails with:
>
> something is wrong, mod_perl 2.0 build should have supplied all the
> needed information to run the tests. Please post
> lib/Apache/BuildConfig.pm along with the bug report at
> /home/stas/apache.org/mp2-cvs/Apache-Test/lib/Apache/TestConfig.pm line
> 349.
> +--------------------------------------------------------+
> | Please file a bug report: http://perl.apache.org/bugs/ |
> +--------------------------------------------------------+
>
> A-T rightfully fails since it doesn't know where apxs/httpd are (they
> were never supplied).
>
> 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.
>
> Do we need to support the build against the source for any other reason
> than static build?
>
> 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).
> ------------
>
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org