specifically what operations need make or nmake? i need to
know so i can provide appropriately-prepared files so it
won't try to run it. this is so i can run it on systems
that don't have a developer environment installed..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Geoffrey Young wrote:
% t/TEST -help
...
and in case it's not obvious (and for the archives) the '...' represents a
slurry of options from TestRun.pm, whereas the shown 'configuration options'
represent those from TestConfig.pm. I was wondering where -preamble and
some others were and it took me
Geoffrey Young wrote:
% t/TEST -help
...
and in case it's not obvious (and for the archives) the '...' represents a
slurry of options from TestRun.pm, whereas the shown 'configuration options'
represent those from TestConfig.pm. I was wondering where -preamble and
some others were and it took me
> % t/TEST -help
>
> ...
and in case it's not obvious (and for the archives) the '...' represents a
slurry of options from TestRun.pm, whereas the shown 'configuration options'
represent those from TestConfig.pm. I was wondering where -preamble and
some others were and it took me a minute :)
>
David Wheeler wrote:
Are all of the options parsed by Apache::TestMM::filter_args()
documented somewhere?
It accepts all the configuration options that you'd normall pass to t/TEST.
i.e.
% t/TEST -help
...
configuration options:
-access_module_name access module name
-apxs locat
Are all of the options parsed by Apache::TestMM::filter_args()
documented somewhere?
Thanks,
David
> The analysis of the problem pointed to by the url above looks right to
> me. I came to the same conclusion, that 1.3 and 2.0 are fundamentally
> different in how they handle/respond to chunked request bodies. 1.3 is
> not going to change so may as well work around it. I am not a perl
> programme
