Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: "Rick Hellicar (QMP)" To: "'cygwin AT cygwin DOT com'" Subject: RE: Compiling/running code that used to work okay! Date: Fri, 3 May 2002 17:07:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Larry Hall wrote: > At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote: >> Hi all, >> >> I'm modifying some old code I last compiled in October 2000. The code uses a 3rd-party DLL, which >> comes with an import library. It used to link without fuss against that import library and run perfectly. >> >> I've moved on to cygwin_1.3.10, gcc version 2.95.3-5, and I now get a host of "undefined references". My code >> is (currently) the same as before, and so are the DLL and its import library. Any idea why it used to compile/link >> but doesn't anymore? > Not with the given level of details, no. Thanks for taking the time to reply, Larry. I *finally* traced the problem; the include files associated with the DLL add the two attributes "cdecl" and "stdcall" to the function prototypes, but only if WIN32 or __WIN32__ are defined. I modified the .h file to test for __CYGWIN__ as well, and now everything's hunky dory. Thanks again. Rick -- 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/