From: "Alexandre Devaure" Newsgroups: comp.os.msdos.djgpp References: <8AyN4.3395$fv3 DOT 5373032 AT nnrp6 DOT proxad DOT net> <8e6f79$99u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> Subject: Re: attribute stdcall Lines: 22 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: Date: Wed, 26 Apr 2000 13:50:06 GMT NNTP-Posting-Host: 194.51.236.59 X-Complaints-To: abuse AT proxad DOT net X-Trace: nnrp5.proxad.net 956757006 194.51.236.59 (Wed, 26 Apr 2000 15:50:06 CEST) NNTP-Posting-Date: Wed, 26 Apr 2000 15:50:06 CEST Organization: Guest of ProXad - France To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker a écrit dans le message : 8e6f79$99u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE... > Alexandre Devaure wrote: > > Has sombody ever had compilation problem with a function declared with the > > attribute stdcall with gcc 2.95? > > I've never used anything of this, but from looking at the error > messages you show, I'd try adding the __attribute((stdcall)) to the > function implementation. That attribute becomes part of the 'type' of > the function, so it's no big surprise that the compiler complains if > the implementation doesn't use the exact same type as the prototype > declaration. Yes, I need to add the attribute to the function implementation. Thing that wasn't necessary with the gcc 2.8 and isn't say in the doc. thanks for all, Alex