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 <[EMAIL PROTECTED]> 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 resolve the problems yourself, with Graham's suggestion wrt to the vcproj file, or 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" <[EMAIL PROTECTED]> To: "python-dev list" <python-dev@httpd.apache.org> Sent: Thursday, November 09, 2006 11:00 AM Subject: 3.3 build problem on Win32 > 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" <[EMAIL PROTECTED]> > 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) > > >> The mod_python 3.3-0-dev-20061109 tarball is available for testing. >> >> We are almost ready for a 3.3.0 release. It's been a while since >> we've had extensive testing of trunk and I think it would be wise to >> have a preliminary testing round. Unless there are huge problems >> we'll do an official beta next week. If it looks *really* good we >> might even jump right to the release. >> >> At this point svn trunk should be considered frozen execpt to fix >> issues that testing exposes or minor documentation changes. >> >> Here are the rules: >> >> In order for a file to be officially announced, it has to be tested by >> developers on the dev list. Anyone subscribed to this list can (and >> should feel obligated to :-) ) test it, and provide feedback *to >> _this_ >> list*! (Not the [EMAIL PROTECTED]
