[mod_python] Compiling mod_python HP-UX

Buehre, Joseph R joseph.r.buehre at boeing.com
Sat Oct 28 19:50:17 EDT 2006


 python was built with --enable-shared


Thanks, 
Joe Buehre 
Mission Critical Systems Support 
314-791-9725

 mailto:joseph.r.buehre at boeing.com


-----Original Message-----
From: Graham Dumpleton [mailto:grahamd at dscpl.com.au] 
Sent: Saturday, October 28, 2006 6:47 PM
To: mod_python at modpython.org 'mod_python at modpython.org'
Cc: Buehre, Joseph R
Subject: Re: [mod_python] Compiling mod_python HP-UX

Please try and keep discussion on the list.

Bar suggesting you rebuild Python with:

   --enable-shared

to configure, I don't know. But others might, thus why good idea to keep
it all information on the list as some part of it may mean something to
someone.

Begin forwarded message:

> From: "Buehre, Joseph R" <joseph.r.buehre at boeing.com>
> Date: 29 October 2006 10:41:04 AM
> To: "Graham Dumpleton" <grahamd at dscpl.com.au>
> Subject: RE: [mod_python] Compiling mod_python HP-UX
>
> Just some added information after running make dso it creates a 
> mod_python.so link in the "src" directory pointing to 
> .libs/mod_python.so which does not exist. The only files in the 
> ".libs"
> directory is mod_python.a, mod_python.la link pointing to 
> ../mod_python.la, mod_python.lai and mod_python.sl files
>
>
> Thanks,
> Joe Buehre
> Mission Critical Systems Support
> 314-791-9725
>
>  mailto:joseph.r.buehre at boeing.com
>
>
> -----Original Message-----
> From: Graham Dumpleton [mailto:grahamd at dscpl.com.au]
> Sent: Tuesday, October 24, 2006 5:00 PM
> To: Buehre, Joseph R
> Cc: mod_python at modpython.org
> Subject: Re: [mod_python] Compiling mod_python HP-UX
>
> Buehre, Joseph R wrote ..
>> Has anyone sucessfully compiled mod_python on HP-UX with apache 2.0 
>> and the last release of mod_python. My compile comes out with no 
>> errors but does not create the mod_python.so file.
>
> It has been noted that although sometimes a .so isn't generated and 
> errors are generated, but the build process still continues.
> Because the
> creation of the .so is not the last thing in the build, the actual 
> error messages can be buried in the middle of the build output. Thus, 
> make sure you go back through the whole build output looking for 
> anything that looks like an error or warning, don't expect that it 
> will be at the end and that the build will stop with an error.
>
> Also trying going:
>
>   cd src
>   make dso
>
> What is the output you get from doing just that?
>
> Graham



More information about the Mod_python mailing list