This is the mail archive of the
mailing list for the Cygwin project.
Re: Python 3.2 cygport script
- From: Jason Tishler <jason at tishler dot net>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 18 Jul 2012 15:36:25 -0400
- Subject: Re: Python 3.2 cygport script
- References: <20120614185640.GE2904@tishler.net> <4FDAEB6E.email@example.com> <20120622171808.GR3556@tishler.net> <1340697070.5432.3.camel@YAAKOV04> <4FF6EC83.firstname.lastname@example.org>
On Fri, Jul 06, 2012 at 08:47:47AM -0500, Yaakov (Cygwin/X) wrote:
> On 2012-06-26 02:51, Yaakov (Cygwin/X) wrote:
> >On Fri, 2012-06-22 at 13:18 -0400, Jason Tishler wrote:
> >>I really appreciate your feedback. Can you post your WIP Python 3.2
> >>cygport script and patches?
> I just pushed an additional patch to fix ctypes for 3.2.
Thanks for the above.
BTW, to get the _dbm module to build I had to change 3.1-dbm.patch as
@@ -1077,6 +1077,8 @@
ndbm_libs = ['ndbm']
+ elif self.compiler.find_library_file(lib_dirs, 'gdbm_compat'):
+ ndbm_libs = ['gdbm_compat']
ndbm_libs = 
print("building dbm using ndbm")
Additionally, I removed --with-dbmliborder=gdbm from CYGCONF_ARGS.
Note that the above changes make the 3.2 _dbm build more like the 2.6
one. Did the _dbm module build for you with your python3-3.2.3-1.cygport
script? It didn't when I tried it. Is the above approach OK? Or, can
you think of a better way?