quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Robbins" <je...@livedata.com>
Subject 3.3 build problem on Win32
Date Thu, 09 Nov 2006 16:00:11 GMT
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 

> 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 mod_python@modpython.org list, and preferably not me
> personally).
> The files are (temporarily) available here:
> http://people.apache.org/~jgallacher/mod_python/dist/
> http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz
> http://people.apache.org/~jgallacher/mod_python/dist/mod_python-3.3.0-dev-20061109.tgz.md5
> Please download it, then do the usual
> $ ./configure --with-apxs=/wherever/it/is
> $ make
> $ (su)
> # make install
> Then (as non-root user!)
> $ make check
> Or for you Windows folks
> $ cd test
> $ python test.py
> And see if any tests fail. If they pass, send a +1 to the list, if they
> fail, send the details (the versions of OS, Apache, Apache-mpm, Python,
> the test output, and suggestions, if any).
> Please present your test results in the following format:
> +1 OS version, Apache version (apache mpm), Python Version
> For example:
> +1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
> Presenting your information in a consistent format will help in
> tabulating the results. You can include additional information in each
> section, just don't use extra commas. There is no need to include the
> mod_python version in this string as that information is available in
> the email subject. Who knows, one day I may actually write a script to
> extract this information automatically.  :)
> Thank you for your assistance,
> Jim Gallacher

View raw message