From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2679 invoked by alias); 11 Feb 2002 18:44:11 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 2596 invoked from network); 11 Feb 2002 18:44:06 -0000 Received: from unknown (HELO alageremail1.agere.com) (192.19.192.106) by sources.redhat.com with SMTP; 11 Feb 2002 18:44:06 -0000 Received: from rderelay.agere.com (rderelay.agere.com [135.15.172.48]) by alageremail1.agere.com (8.10.2+Sun/8.10.2) with ESMTP id g1BIgPG23827 for ; Mon, 11 Feb 2002 13:42:25 -0500 (EST) Received: from almail.agere.com by rderelay.agere.com (8.9.3+Sun/EMS-1.5 sol2) id NAA05759 for ; Mon, 11 Feb 2002 13:44:03 -0500 (EST) Received: from PAI820G1006951 by almail.agere.com (8.9.3+Sun/EMS-1.5 sol2) id NAA09720; Mon, 11 Feb 2002 13:44:03 -0500 (EST) From: "Gerald S. Williams" To: Subject: Re: "Best" way to build a DLL? Date: Mon, 11 Feb 2002 10:44:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal In-Reply-To: X-SW-Source: 2002-02/txt/msg00541.txt.bz2 > Warning: resolving __Py_NoneStruct by linking to \ > __imp___Py_NoneStruct (auto-import) > Warning: resolving _PyInt_Type by linking to \ > __imp__PyInt_Type (auto-import) I poked around a bit and found out that those "Warnings" were actually indicating that global variables were being linked by the auto-importer. When you link to the DLL directly, you get seg faults if you refer to those variables. (I guess I *was* lucky--I hadn't seen this since I hadn't executed the code making those references). I had to change my builds to use the import library in order to eliminate the seg faults when referring to those variables. It looks like you can use just GCC, though. Chuck Wilson's C example in dllhelpers-0.40.0 bears this out, and shows how to create an import library at the same time without the need for a .def file (using -Wl,--out-implib and -Wl,--export-all-symbols). I'm not sure why those are reported as warnings. Is there an easy way to disable them? -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:gsw@agere.com O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18109-3286 : mobile:908-672-7592 O- -- 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/