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: Mon, 6 Aug 2001 13:51:53 -0400 From: Jason Tishler To: Peter Bienstman Cc: nhv@cape.com, cygwin@cygwin.com Subject: Re: building Python extension modules - crash on import Message-ID: <20010806135153.N1888@dothill.com> Mail-Followup-To: Peter Bienstman , nhv@cape.com, cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000201c11e88$b3534950$0454c19d@intec.rug.ac.be> User-Agent: Mutt/1.3.18i Organization: Dot Hill Systems Corp. Peter, On Mon, Aug 06, 2001 at 05:01:41PM +0200, Peter Bienstman wrote: > > Try the attached Makefiles I knew that Norman would swoop down and save the day! > Wow, that worked! It's the USE_DL_IMPORT macro that clinched it. I got off > on the wrong foot by using the gcc_linux makefile in the Boost directory, > rather than the more general gcc makefile. BTW, the USE_DL_IMPORT macro, etc. is set automatically if the Cygwin Python extension is built via the Distutils or Misc/Makefile.pre.in method. My recommendation is to try to use Distutils, if possible, when building Python extensions. Jason -- Jason Tishler Director, Software Engineering Phone: 732.264.8770 x235 Dot Hill Systems Corp. Fax: 732.264.8798 82 Bethany Road, Suite 7 Email: jason@tishler.net Hazlet, NJ 07730 USA WWW: http://www.dothill.com -- 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/