Geoffrey Young wrote:
Stas Bekman wrote:
Unless I'm blind again, I can't see how 3rd party modules that use
Apache C API can build when a threaded perl is used with mod_perl 1.0.
In the current cvs, "apache_inc.h" doesn't get included at all with
-DPERL_THREADS and therefore the build fails
Gerald Richter wrote:
1) build: something is missing from README because
xsbuilder/xs_generate.pl was looking for xsbuilder/maps and couldn't
find it. I've added a symlink similar to xsbuilder/xs and then it
worked. shouldn't it look for xsbuilder/xs/maps instead?
makeing the symlink was the r
Gerald Richter wrote:
I had submitted a patch for adding this to the generic test suite. maybe
you can steal some of the code:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=103919146817077&w=2
As far as I see it only check if the generated POD is syntactical ok, or
does it more?
n
>
> I had submitted a patch for adding this to the generic test suite. maybe
> you can steal some of the code:
>
> http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=103919146817077&w=2
>
As far as I see it only check if the generated POD is syntactical ok, or
does it more?
The problem is less
>
> 1) build: something is missing from README because
> xsbuilder/xs_generate.pl was looking for xsbuilder/maps and couldn't
> find it. I've added a symlink similar to xsbuilder/xs and then it
> worked. shouldn't it look for xsbuilder/xs/maps instead?
>
makeing the symlink was the right thing to
Stas Bekman wrote:
Unless I'm blind again, I can't see how 3rd party modules that use
Apache C API can build when a threaded perl is used with mod_perl 1.0.
In the current cvs, "apache_inc.h" doesn't get included at all with
-DPERL_THREADS and therefore the build fails. Spotted with
Apache::
The next steps that
should
be done is to verify that the content of the pods is correct.
I had submitted a patch for adding this to the generic test suite. maybe
you can steal some of the code:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=103919146817077&w=2
HTH
--Geoff
---