Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 27 Sep 2001 21:12:52 -0400 From: Jason Tishler To: "Darrell R. Hougen" Cc: cygwin@cygwin.com, darrell.r.hougen@lmco.com Subject: Re: Problem linking python extensions Message-ID: <20010927211252.S1356@dothill.com> Mail-Followup-To: "Darrell R. Hougen" , cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BB3515D.C01127D1@lmco.com> User-Agent: Mutt/1.3.18i On Thu, Sep 27, 2001 at 10:18:37AM -0600, Darrell R. Hougen wrote: > Any help is greatly appreciated. I'm still not clear whether you are trying to build a Cygwin or Win32 Python extension. Which are you trying to build? My suggestion is to use Distutils -- it knows have to generate the right command lines to build either a Cygwin or Win32 Python extension. See the following: http://www.python.org/doc/current/dist/dist.html I don't believe that you have generate a valid extension -- at least from exporting the init function point of view. Trying using objdump (or dumpbin if you have MSVC++) to verify that your extension is exporting initTermObject (not _initTermObject). For example: $ objdump -p /usr/lib/python2.1/lib-dynload/zlib.dll | fgrep init [ 0] initzlib BTW, you may find better help on the Distutils list: distutils-sig@python.org Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/