Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: <42D85C22.6080307@familiehaase.de>
Date: Sat, 16 Jul 2005 03:00:18 +0200
From: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: undefined reference to `_CAPI_INSTALLED AT 0', why?
References: <SERRANO59KuERIqVDok0000030e AT SERRANO DOT CAM DOT ARTIMI DOT COM>
In-Reply-To: <SERRANO59KuERIqVDok0000030e@SERRANO.CAM.ARTIMI.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Dave,

>>So why does the compiler creats a reference to _CAPI_INSTALLED AT 0 or
>>is it the linker who wants to resolve CAPI_INSTALLED with @0 attached.
> 
> 
>   Has the definition of APIENTRY has changed between the mfr's build from
> which the import library came and the build from which you generated your
> import lib?

Many thanks, that is it:

#  define APIENTRY __attribute__((stdcall))


Gerrit
-- 
=^..^=


--
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/