11-13-06 01:13 PM
sorry for the confusion.
I added the file to vcproj
the build ran correctly
my leak tests passed with flying colors
-----Original Message-----
From: Jim Gallacher <jpg@jgassociates.ca>
Date: Thursday, Nov 9, 2006 3:59 pm
Subject: Re: apache 2.2.3 mod_python 3.3 on win32 looking good
I'm a little confused by your reply to your own message, Jeff. Did you resol
ve the problems yourself, with Graham's suggestion wrt to the vcproj file, o
r something else.
Jim
Jeff Robbins wrote:
No memory leaks; no OS handle leaks; no Python object leaks
I haven't run the tests yet as I have to leave until Monday. Perhaps
another win32 user can do so?
----- Original Message ----- From: "Jeff Robbins" <jeffr@livedata.com>
To: "python-dev list" <python-dev@httpd.apache.org>
Sent: Thursday, November 09, 2006 11:00 AM
Subject: 3.3 build problem on Win32
[vbcol=seagreen]
> Two build problems...one I could fix and one I couldn't
> the fixable one is that on Win32 libapr.lib is called libapr-1.lib
> (not sure why) and libaprutil.lib is called libaprutil-1.lib
>
> the one I'm lost with is this:
>
> _apachemodule.obj : error LNK2019: unresolved external symbol
> __imp__MpFinfo_New referenced in function _mp_stat
> requestobject.obj : error LNK2019: unresolved external symbol
> __imp__MpFinfo_Type referenced in function _setreq_recmbr
> requestobject.obj : error LNK2019: unresolved external symbol
> __imp__MpFinfo_FromFinfo referenced in function _getreq_rec_fi
>
> .\Release/mod_python.so : fatal error LNK1120: 3 unresolved externals
>
> What are these functions?
>
> - Jeff
>
>
> ----- Original Message ----- From: "Jim Gallacher" <jpg@jgassociates.ca>
> To: "python-dev list" <python-dev@httpd.apache.org>
> Sent: Thursday, November 09, 2006 9:00 AM
> Subject: mod_python 3.3.0-dev-20061109 available for testing (release
> candidate)
>
>
[ Post a follow-up to this message ]
| 
