Opened at 2009-06-13T18:17:22Z
Closed at 2009-06-30T17:36:21Z
#23 closed defect (fixed)
can't build Python module for Python 2.6 with MinGW
| Reported by: | zooko | Owned by: | bdew |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Version: | 0.5.1 | Keywords: | win32 portability mingw |
| Cc: | bdew | Launchpad Bug: |
Description
Black Dew had trouble building with mingw, and he eventually traced the problem to this:
http://allmydata.org/pipermail/tahoe-dev/2009-June/001978.html
He tested the fix of removing the 'time' symbol from msvcr90.a and that allowed him to build successfully.
This appears to be the same issue as http://lists.zerezo.com/mingw-users/msg11190.html and may also be related to http://sourceforge.net/tracker/index.php?func=detail&aid=2134161&group_id=2435&atid=302435 .
Here is the ticket on the MinGW tracker: https://sourceforge.net/tracker/?func=detail&aid=2805976&group_id=2435&atid=302435
Change History (5)
comment:1 Changed at 2009-06-21T05:14:48Z by zooko
- Cc bdew added
comment:2 Changed at 2009-06-21T05:15:25Z by zooko
- Owner set to bdew
comment:3 Changed at 2009-06-21T06:17:37Z by bdew
I've restored mingw on my work mcomputer to it's original state, built and ran tests fine.
I'll remove the modifications on the buildslave too when I get home.
comment:4 Changed at 2009-06-21T15:36:23Z by bdew
Ok, the buildslave is now using unmodified mingw, and everything works with the patch.
comment:5 Changed at 2009-06-30T17:36:21Z by zooko
- Resolution set to fixed
- Status changed from new to closed
Fixed by [20090621051014-92b7f-3489ac19e9b0fde0c44943d20b603b860a89bf1f]. Black Dew, could you please try pycryptopp with this patch on a system with a pristine upstream MinGW?