From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References: <000001c7adeb$04468a00$0cd39e00$@mills@novaspeech.com>
Subject: RE: dll link error using Cygwin gcc
Date: Wed, 13 Jun 2007 19:48:23 +0100
Message-ID: <01cc01c7adeb$6b351830$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <000001c7adeb$04468a00$0cd39e00$@mills@novaspeech.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 13 June 2007 19:45, Harold Mills wrote:

> As Dave Korn and Brian Dessent both pointed out, my problem was that gcc was
> compiling Hello.c with the default cdecl calling convention, but the library
> I wanted to link to uses the stdcall convention. Adding __stdcall to the
> function declarations in the header file eci.h fixed the problem. Dave
> suggested using the --enable-stdcall-fixup link option, which from the ld
> documentation did seem like it would do the trick, but I couldn't get it to
> work. I specified it to gcc as -Wl,--enable-stdcall-fixup, but still got the
> "undefined reference" error message.

  In any case, Brian was right and my suggestion was wrong: if the library was
compiled with a different calling convention, bodging the symbols to match up
isn't the right thing to do, because the code will go wrong at runtime.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/