You are viewing a plain text version of this content. The canonical link for it is here.

Posted to modperl@perl.apache.org by "Philippe M. Chiasson" <go...@apache.org> on 2008/04/02 08:17:31 UTC

[RELEASE CANDIDATE] mod_perl-1.31 RC4

The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is ready. It can be downloaded here:

http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz

MD5:  ba12ce36c4c738bccfa93ab646a6824c
SHA1: 2de6ce29f44505cfdca34b7aa6499d961c72953b

Please give it a spin in your favorite configuration and report
any problems. Especially needed against Perl-5.10.

The summary of what has changed since 1.30 are (from Changes):

Fix potential segfault when the environment contains
NULL values [Mike Schilli]

Fix static APACI build against newer apache-1.3.38+
[Gozer]

Fixed modules/regex.t test 4 on Win32
[Steve Hay]

Avoid possible segfault when PerlFreshRestart is On.
[Michael Rendell <mi...@cs.mun.ca>]

Prevent segfault when running with perl >= 5.9.3
[Steve Hay]

Fix shared libary extensions on Win32 to be .dll not .so
[Nikolay Ananiev <an...@thegdb.com>]

Patch to mod_perl.dsp to remove /D _WINSOCK2API_ on Win32
for perl >= 5.8.6 [Steve Hay]

-- 
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by Steve Hay <St...@planit.com>.

Steve Hay wrote:
[...]
> Thus, the end of my mod_perl build goes like this: 
> 
>         msdev src\modules\win32\mod_perl.dsp  /MAKE "mod_perl - Win32
> Release" /USEENV
> --------------------Configuration: mod_perl - Win32
> Release--------------------
> Compiling...
> Apache.c
> Connection.c
> Constants.c
> File.c
> Log.c
> ModuleConfig.c
> ModuleConfig.xs(72) : warning C4715: 'vector_from_sv' : not all
> control paths return a value
> mod_perl.c
> mod_perl_opmask.c
> perl_config.c
> perl_util.c
> perlio.c
> perlxsi.c
> Server.c
> Table.c
> URI.c
> Util.c
> Linking...
>    Creating library Release/mod_perl.lib and object
> Release/mod_perl.exp 
> 
> mod_perl.so - 0 error(s), 1 warning(s)
> 
> Notice the "Win32 Release" configuration there. So you need to rebuild
> mod_perl.so in debug mode after running the initial "nmake". You can
> do so by running the following command (from the top-level directory):
> 
> msdev src\modules\win32\mod_perl.dsp  /MAKE "mod_perl - Win32 Debug"

Oops! I missed the " /USEENV" off the end of that command-line. You need
that too, as per the original command-line shown above.


[...]
> PerlIOUnix_setfd() is calling PerlIOUnix_refcnt_inc(fd)
> with fd 0. Simply put a breakpoint on line 2548 in perlio.c and it
> crashes the first time it hits it. Stepping inside
> PerlIOUnix_refcnt_inc() I find that it reaches the line
> 
> MUTEX_LOCK(&PL_perlio_mutex);
> 
> (which is only present in the USE_ITHREADS case) and crashes there.
> PL_perlio_mutex itself is a valid struct, but all its members are 0 or
> 0x00000000. I don't know if that's normal.
> 
> On Win32, MUTEX_LOCK(m) seems to be #defined as
> EnterCriticalSection(m) (in win32\win32thread.h, given that
> DONT_USE_CRITICAL_SECTION is never #defined anywhere). Hmm. The
> comment there says "Critical Sections used instead of mutexes:
> lightweight, but can't be communicated to child processes ...". I
> wonder if the other case in that #ifndef might be worth trying,
> although that wouldn't be the default build option so we shouldn't
> need to do that... Perhaps Jan can assist here? 

I tried a build with DONT_USE_CRITICAL_SECTION defined, but it behaves
exactly the same except that the other #definition of MUTEX_LOCK(m) is
now used, namely:

#  define MUTEX_LOCK(m) \
    STMT_START {						\
	if (WaitForSingleObject(*(m),INFINITE) == WAIT_FAILED)	\
	    Perl_croak_nocontext("panic: MUTEX_LOCK");		\
    } STMT_END

so I get a "panic: MUTEX_LOCK" error instead of the crash! Or at least,
that's the string shown in "pat" in Perl_croak_nocontext() by the
debugger, but the console output actually says:

parse: Bad file descriptor

I'm not sure if that's any kind of clue.

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

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by Steve Hay <St...@planit.com>.

Steve Hay wrote:
> Philippe M. Chiasson wrote:
>> Steve Hay wrote:
>>> Philippe M. Chiasson wrote:
>>>> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is
>>>> ready. It can be downloaded here:
>>>> 
>>>> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz
>>> 
>>> All tests OK using VC6 on WinXP with apache 1.3.39 and perl 5.10.0
>>> built without USE_MULTI, USE_ITHREADS or USE_IMP_SYS.
>>  >
>>> Crashes on startup with apache 1.3.41 and perl 5.10.0 built with
>>> default options (i.e. with USE_MULTI, USE_ITHREADS or USE_IMP_SYS).
>> 
>> Any chance to try and narrow it down a little bit more between these
>> 3?
> 
> I tried with USE_MULTI + USE_ITHREADS but no USE_IMP_SYS and it still
> crashes, so it must be USE_ITHREADS that is doing it. (USE_MULTI is a
> pre-requisite for USE_ITHREADS, so I can't try without that, and I've
> a feeling that USE_MULTI on its own is useless and might not even
> build.) 
> 
> So basically, mp1 crashes with ithreaded builds of perl.
> 

This is hopefully now fixed with r719313. Sorry it took so long!!! [I
haven't been working on it all that time ;-)]

Can some other people please give it a whirl, and if it looks good then
perhaps we can have an RC5?

See also r719315, which fixes a problem I found building libapreq1.

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

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by Steve Hay <St...@planit.com>.

Philippe M. Chiasson wrote:
> Steve Hay wrote:
>> Philippe M. Chiasson wrote:
>>> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is
>>> ready. It can be downloaded here:
>>> 
>>> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz
>> 
>> All tests OK using VC6 on WinXP with apache 1.3.39 and perl 5.10.0
>> built without USE_MULTI, USE_ITHREADS or USE_IMP_SYS.
>  >
>> Crashes on startup with apache 1.3.41 and perl 5.10.0 built with
>> default options (i.e. with USE_MULTI, USE_ITHREADS or USE_IMP_SYS).
> 
> Any chance to try and narrow it down a little bit more between these
> 3? 

I tried with USE_MULTI + USE_ITHREADS but no USE_IMP_SYS and it still
crashes, so it must be USE_ITHREADS that is doing it. (USE_MULTI is a
pre-requisite for USE_ITHREADS, so I can't try without that, and I've a
feeling that USE_MULTI on its own is useless and might not even build.)

So basically, mp1 crashes with ithreaded builds of perl.

> 
> I've finally managed to reproduce this crash myself. I've had to bite
> the bullet and get myself a Win32 VM I can actually build all this
> stuff under. 

:-)

> 
> Haven't managed to get a usefull debugging session running yet. Can't
> seem to get VC6 to pick up/display debugging symbols. Any hits from
> folks here with stronger win-foo than me ?

Obviously you need to build Apache and Perl in a debug configuration (I
assume you've figured out how to do that--I use src\makefile.win with
the "installd" option for Apache, and win32\Makefile with CFG=Debug for
Perl). Building Perl modules should then pick up the fact that Perl is
built in a debug configuration and build the modules likewise. This
works in general for ExtUtils-MakeMaker (and Module-Build) modules, and
hence for the Apache::* modules, but the mod_perl.so build doesn't seem
to pick up on it. Thus, the end of my mod_perl build goes like this:

        msdev src\modules\win32\mod_perl.dsp  /MAKE "mod_perl - Win32
Release" /USEENV
--------------------Configuration: mod_perl - Win32
Release--------------------
Compiling...
Apache.c
Connection.c
Constants.c
File.c
Log.c
ModuleConfig.c
ModuleConfig.xs(72) : warning C4715: 'vector_from_sv' : not all control
paths return a value
mod_perl.c
mod_perl_opmask.c
perl_config.c
perl_util.c
perlio.c
perlxsi.c
Server.c
Table.c
URI.c
Util.c
Linking...
   Creating library Release/mod_perl.lib and object Release/mod_perl.exp

mod_perl.so - 0 error(s), 1 warning(s)

Notice the "Win32 Release" configuration there. So you need to rebuild
mod_perl.so in debug mode after running the initial "nmake". You can do
so by running the following command (from the top-level directory):

msdev src\modules\win32\mod_perl.dsp  /MAKE "mod_perl - Win32 Debug"

That spits out a load of warnings on my system which the release mode
build didn't do, but does create a debug build mod_perl.so.

After that you need to run "nmake test" to get a httpd.conf created in
t/conf. That also copies the *release build* mod_perl.so from
src\modules\win32\Release into t\modules, so afterwards you need to
overwrite it with the *debug build* version from
src\modules\win32\Debug.

Then you're ready to debug Apache.exe. I normally start up Dev Studio
from the Command Prompt in which I've built everything so that the PATH
already includes perl\bin and apache. Open a Workspace and browse for
Apache.exe. Then go into Project > Settings, "Debug" tab and set the
"Working directory" to the path of your mod_perl source folder and the
"Program arguments" to specify the path to the httpd.conf file that was
created by "nmake test" earlier, e.g.:

"-f C:\Temp\mod_perl-1.31-rc4\t\conf\httpd.conf"

You'll also need to select "Additional DLLs" from the "Category"
drop-down and add both perl510.dll (or whatever version you're using)
and mod_perl.so to the list, otherwise VC6 doesn't pick up symbols from
DLLs! (VC8 onwards does automatically pick up DLLs as/when they're
loaded.)

Hope that helps!

Below is the stacktrace that I get when it crashes (using perl-5.10.0).
PerlIOUnix_setfd() is calling PerlIOUnix_refcnt_inc(fd) with fd 0.
Simply put a breakpoint on line 2548 in perlio.c and it crashes the
first time it hits it. Stepping inside PerlIOUnix_refcnt_inc() I find
that it reaches the line

MUTEX_LOCK(&PL_perlio_mutex);

(which is only present in the USE_ITHREADS case) and crashes there.
PL_perlio_mutex itself is a valid struct, but all its members are 0 or
0x00000000. I don't know if that's normal.

On Win32, MUTEX_LOCK(m) seems to be #defined as EnterCriticalSection(m)
(in win32\win32thread.h, given that DONT_USE_CRITICAL_SECTION is never
#defined anywhere). Hmm. The comment there says "Critical Sections used
instead of mutexes: lightweight, but can't be communicated to child
processes ...". I wonder if the other case in that #ifndef might be
worth trying, although that wouldn't be the default build option so we
shouldn't need to do that... Perhaps Jan can assist here?

NTDLL! 7c918fea()
NTDLL! 7c90104b()
PerlIOUnix_setfd(interpreter * 0x003f6e88, _PerlIO * * 0x00823594, int
0, int 0) line 2548 + 9 bytes
PerlIOUnix_open(interpreter * 0x003f6e88, _PerlIO_funcs * 0x281f9988
_PerlIO_unix, PerlIO_list_s * 0x008237e0, long 0, const char *
0x281eb39d, int 0, int 0, int 0, _PerlIO * * 0x00823594, int 0, sv * *
0x00000000) line 2625 + 21 bytes
PerlIOBuf_open(interpreter * 0x003f6e88, _PerlIO_funcs * 0x281f9b48
_PerlIO_crlf, PerlIO_list_s * 0x008237e0, long 1, const char *
0x281eb39c `string', int 0, int 0, int 0, _PerlIO * * 0x00000000, int 0,
sv * * 0x00000000) line 3685 + 53 bytes
PerlIO_openn(interpreter * 0x003f6e88, const char * 0x00000000, const
char * 0x281eb39c `string', int 0, int 0, int 0, _PerlIO * * 0x00000000,
int 0, sv * * 0x00000000) line 1597 + 50 bytes
PerlIO_fdopen(int 0, const char * 0x281eb39c `string') line 4988 + 29
bytes
PerlIO_stdstreams(interpreter * 0x003f6e88) line 1204 + 12 bytes
PerlIO_resolve_layers(interpreter * 0x003f6e88, const char * 0x00000000,
const char * 0x281d43ac `string', int 1, sv * * 0x0012dabc) line 1486 +
9 bytes
PerlIO_openn(interpreter * 0x003f6e88, const char * 0x00000000, const
char * 0x281d43ac `string', int -1, int 0, int 0, _PerlIO * *
0x00000000, int 1, sv * * 0x0012dabc) line 1568 + 25 bytes
PerlIO_open(const char * 0x00823930, const char * 0x281d43ac `string')
line 4997 + 29 bytes
S_open_script(interpreter * 0x003f6e88, const char * 0x00823930, char 0,
sv * 0x003fb920, int * 0x0012db4c, _PerlIO * * * 0x0012dba0) line 3704 +
14 bytes
S_parse_body(interpreter * 0x003f6e88, char * * 0x00000000, void
(interpreter *)* 0x10026810 mod_perl_xs_init(interpreter *)) line 2053 +
29 bytes
perl_parse(interpreter * 0x003f6e88, void (interpreter *)* 0x10026810
mod_perl_xs_init(interpreter *), int 4, char * * 0x0012dd0c, char * *
0x00000000) line 1650 + 17 bytes
perl_startup(server_rec * 0x009a7040, pool * 0x009a7018) line 704 + 27
bytes
perl_cmd_require(cmd_parms * 0x0012fe78, void * 0x009a8ae8, char *
0x009a8c78) line 621 + 28 bytes
invoke_cmd(const command_struct * 0x10097c20, cmd_parms * 0x0012fe78,
void * 0x009a8ae8, const char * 0x0012de30) line 877 + 18 bytes
ap_handle_command(cmd_parms * 0x0012fe78, void * 0x009a7be0, const char
* 0x0012de18) line 988 + 21 bytes
ap_srm_command_loop(cmd_parms * 0x0012fe78, void * 0x009a7be0) line 1002
+ 20 bytes
ap_process_resource_config(server_rec * 0x009a7040, char * 0x009a8768,
pool * 0x009a7018, pool * 0x009ab0c8) line 1294 + 16 bytes
ap_read_config(pool * 0x009a7018, pool * 0x009ab0c8, char * 0x6ffc76c0
_ap_server_confname) line 1579
apache_main(int 3, char * * 0x009a2698) line 7880 + 24 bytes
main(int 3, char * * 0x009a2698) line 33 + 13 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 7c816fd7()

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

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "Philippe M. Chiasson" <go...@apache.org>.

Steve Hay wrote:
> Philippe M. Chiasson wrote:
>> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is
>> ready. It can be downloaded here: 
>>
>> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz
> 
> All tests OK using VC6 on WinXP with apache 1.3.39 and perl 5.10.0 built
> without USE_MULTI, USE_ITHREADS or USE_IMP_SYS.
 >
> Crashes on startup with apache 1.3.41 and perl 5.10.0 built with default
> options (i.e. with USE_MULTI, USE_ITHREADS or USE_IMP_SYS).

Any chance to try and narrow it down a little bit more between these 3?

I've finally managed to reproduce this crash myself. I've had to bite the
bullet and get myself a Win32 VM I can actually build all this stuff under.

Haven't managed to get a usefull debugging session running yet. Can't
seem to get VC6 to pick up/display debugging symbols. Any hits from folks
here with stronger win-foo than me ?

-- 
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "Philippe M. Chiasson" <go...@apache.org>.

Steve Hay wrote:
> Philippe M. Chiasson wrote:
>> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is
>> ready. It can be downloaded here: 
>>
>> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz
> 
> All tests OK using VC6 on WinXP with apache 1.3.39 and perl 5.10.0 built
> without USE_MULTI, USE_ITHREADS or USE_IMP_SYS.
 >
> Crashes on startup with apache 1.3.41 and perl 5.10.0 built with default
> options (i.e. with USE_MULTI, USE_ITHREADS or USE_IMP_SYS).

Any chance to try and narrow it down a little bit more between these 3?

I've finally managed to reproduce this crash myself. I've had to bite the
bullet and get myself a Win32 VM I can actually build all this stuff under.

Haven't managed to get a usefull debugging session running yet. Can't
seem to get VC6 to pick up/display debugging symbols. Any hits from folks
here with stronger win-foo than me ?

-- 
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

RE: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by Steve Hay <St...@planit.com>.

Philippe M. Chiasson wrote:
> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is
> ready. It can be downloaded here: 
> 
> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz

All tests OK using VC6 on WinXP with apache 1.3.39 and perl 5.10.0 built
without USE_MULTI, USE_ITHREADS or USE_IMP_SYS.

Crashes on startup with apache 1.3.41 and perl 5.10.0 built with default
options (i.e. with USE_MULTI, USE_ITHREADS or USE_IMP_SYS).

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "David E. Wheeler" <da...@kineticode.com>.

On Apr 17, 2008, at 13:31, Philippe M. Chiasson wrote:

>> Yes, that works. I wonder why I didn't have to do it before? Is  
>> this  something that can be worked around?
>
> This is an unexpected side effect of another fix, for static builds.

So is that a yes or a no? :-)

>> The test suite didn't run for me, though. :-(
>
> Correct me if I am wrong, but runnign the mp1 test suite as DSO isn't
> really supported. Needs fixing, but that would take Apache::Test, not
> something I am looking forward doing (I believe there is a patch on  
> that
> somewhere in the archive from me, but it needed more work)

Okay. I was never too worried bout mod_perl 1 tests, anyway, was just  
trying to provide them for feedback here. They all passed when I used  
a static build.

Best,

David


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

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "Philippe M. Chiasson" <go...@apache.org>.

David E. Wheeler wrote:
> On Apr 17, 2008, at 01:33, Philippe M. Chiasson wrote:
> 
>> So you end up with a Makefile that goes like
>>
>> all: libperl.so (thank you Apache)
>>
>> libperl.bundle: (thank you Perl/OSX)
>>
>> Try with:
>>
>> $> make PERL_DLEXT=so
> 
> Yes, that works. I wonder why I didn't have to do it before? Is this  
> something that can be worked around?

This is an unexpected side effect of another fix, for static builds.

> The test suite didn't run for me, though. :-(

Correct me if I am wrong, but runnign the mp1 test suite as DSO isn't
really supported. Needs fixing, but that would take Apache::Test, not
something I am looking forward doing (I believe there is a patch on that
somewhere in the archive from me, but it needed more work)

-- 
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "David E. Wheeler" <da...@kineticode.com>.

On Apr 17, 2008, at 01:33, Philippe M. Chiasson wrote:

> So you end up with a Makefile that goes like
>
> all: libperl.so (thank you Apache)
>
> libperl.bundle: (thank you Perl/OSX)
>
> Try with:
>
> $> make PERL_DLEXT=so

Yes, that works. I wonder why I didn't have to do it before? Is this  
something that can be worked around?

The test suite didn't run for me, though. :-(

benedict# make test
(cd ./apaci && PERL5LIB=/usr/local/src/mod_perl-1.31-rc4/lib: make)
make[1]: Nothing to be done for `all'.
cp t/conf/mod_perl_srm.conf t/conf/srm.conf
./apaci/load_modules.pl
/httpd -f `pwd`/t/conf/httpd.conf -X -d `pwd`/t &
httpd listening on port 8529
will write error_log to: t/logs/error_log
/bin/sh: /httpd: No such file or directory
letting apache warm up...done
/usr/local/bin/perl t/TEST 0
still waiting for server to warm up...............not ok
server failed to start! (please examine t/logs/error_log) at t/TEST  
line 95.
make: *** [run_tests] Error 61

Best,

David

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

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "Philippe M. Chiasson" <go...@apache.org>.

David E. Wheeler wrote:
> On Apr 2, 2008, at 10:21, David E. Wheeler wrote:
> 
>> benedict# make
>> (cd ./apaci && PERL5LIB=/usr/local/src/mod_perl-1.31-rc4/lib: make)
>> make[1]: *** No rule to make target `libperl.so', needed by `lib'.   
>> Stop.
>> make: *** [apxs_libperl] Error 2
>>
>> This is on Mac OS X 10.5.2 with Perl 5.10 compiled like so:
>>
>> sh Configure -des -Duseshrplib -Dperladmin=david@kineticode.com -Dcf_email=david@kineticode.com
>> make
>> make test
>> make install
>>
>> *sigh*. I hope this is something simple.

Yes, apache on OSX picks '.so' as the dynamic library extensions.
Perl, on the other hand, picks '.bundle'

> Anyone have any ideas on this? I'm attempting to compile mod_perl as a  
> DSO outside of the Apache source tree using APXS. There must just be a  
> typo or something somewhere, yes? I mean, this worked for me before…

So you end up with a Makefile that goes like

all: libperl.so (thank you Apache)

libperl.bundle: (thank you Perl/OSX)

Try with:

$> make PERL_DLEXT=so

-- 
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "David E. Wheeler" <da...@kineticode.com>.

On Apr 2, 2008, at 10:21, David E. Wheeler wrote:

> benedict# make
> (cd ./apaci && PERL5LIB=/usr/local/src/mod_perl-1.31-rc4/lib: make)
> make[1]: *** No rule to make target `libperl.so', needed by `lib'.   
> Stop.
> make: *** [apxs_libperl] Error 2
>
> This is on Mac OS X 10.5.2 with Perl 5.10 compiled like so:
>
> sh Configure -des -Duseshrplib -Dperladmin=david@kineticode.com -Dcf_email=david@kineticode.com
> make
> make test
> make install
>
> *sigh*. I hope this is something simple.

Anyone have any ideas on this? I'm attempting to compile mod_perl as a  
DSO outside of the Apache source tree using APXS. There must just be a  
typo or something somewhere, yes? I mean, this worked for me before…

Thanks,

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

Re: [RELEASE CANDIDATE] mod_perl-1.31 RC4

Posted by "David E. Wheeler" <da...@kineticode.com>.

On Apr 1, 2008, at 23:17, Philippe M. Chiasson wrote:

> The mod_perl 1.31 release candidate 4 "Works with Perl 5.10" is  
> ready. It can be downloaded here:
>
> http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc4.tar.gz

Damn!

benedict# tar zxf mod_perl-1.31-rc4.tar.gz
benedict# cd mod_perl-1.31-rc4
benedict# USER=dougm /usr/local/bin/perl Makefile.PL \
 >   USE_APXS=1 \
 >   WITH_APXS=/usr/local/apache/bin/apxs \
 >   USE_DSO=1 \
 >   EVERYTHING=1
Will configure via APXS (apxs=/usr/local/apache/bin/apxs)
Will configure via APACI (DSO enabled)
PerlDispatchHandler.........enabled
PerlChildInitHandler........enabled
PerlChildExitHandler........enabled
PerlPostReadRequestHandler..enabled
PerlTransHandler............enabled
PerlHeaderParserHandler.....enabled
PerlAccessHandler...........enabled
PerlAuthenHandler...........enabled
PerlAuthzHandler............enabled
PerlTypeHandler.............enabled
PerlFixupHandler............enabled
PerlHandler.................enabled
PerlLogHandler..............enabled
PerlInitHandler.............enabled
PerlCleanupHandler..........enabled
PerlRestartHandler..........enabled
PerlStackedHandlers.........enabled
PerlMethodHandlers..........enabled
PerlDirectiveHandlers.......enabled
PerlTableApi................enabled
PerlLogApi..................enabled
PerlUriApi..................enabled
PerlUtilApi.................enabled
PerlFileApi.................enabled
PerlConnectionApi...........enabled
PerlServerApi...............enabled
PerlSections................enabled
PerlSSI.....................enabled
Will run tests as User: 'nobody' Group: 'wheel'
Configuring mod_perl for building via APXS
  + Creating a local mod_perl source tree
  + Setting up mod_perl build environment (Makefile)
  + id: mod_perl/1.31-rc4
  + id: Perl/v5.10.0 (darwin) [/usr/local/bin/perl]
Now please type 'make' to build libperl.so
Checking CGI.pm VERSION..........ok
Checking for LWP::UserAgent......ok
Checking for HTML::HeadParser....ok
Checking if your kit is complete...
Looks good
Writing Makefile for Apache
Writing Makefile for Apache::Connection
Writing Makefile for Apache::Constants
Writing Makefile for Apache::File
Writing Makefile for Apache::Leak
Writing Makefile for Apache::Log
Writing Makefile for Apache::ModuleConfig
Writing Makefile for Apache::PerlRunXS
Writing Makefile for Apache::Server
Writing Makefile for Apache::Symbol
Writing Makefile for Apache::Table
Writing Makefile for Apache::URI
Writing Makefile for Apache::Util
Writing Makefile for mod_perl
benedict# make
(cd ./apaci && PERL5LIB=/usr/local/src/mod_perl-1.31-rc4/lib: make)
make[1]: *** No rule to make target `libperl.so', needed by `lib'.   
Stop.
make: *** [apxs_libperl] Error 2

This is on Mac OS X 10.5.2 with Perl 5.10 compiled like so:

sh Configure -des -Duseshrplib -Dperladmin=david@kineticode.com -Dcf_email=david@kineticode.com
make
make test
make install

*sigh*. I hope this is something simple.

Thanks for all your work on this, Philippe.

David



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