On 7/11/2012 14:51, Peter Schaefer wrote:
> Hi!
> 
> I'm using the recent rubenvb-gcc-4.7.1 release and tried to compile an 
> application using TAPI, however tapi.h cannot be 
> compiled:
> 
>> c:\mingw32\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/tapi.h:2074:107:
>>  error: declaration of C function 'LONG lineAddProviderW(LPCWSTR, HWND, 
>> LPDWORD)' conflicts with
>> c:\mingw32\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/tapi.h:2072:1:
>>  error: previous declaration 'LONG lineAddProviderW(LPCSTR, HWND, LPDWORD)' 
>> here
> 
> This is because the whole list of
> 
>> #define yadayada __MINGW_NAME_AW(yadayada)
> 
> is located *before* the function declarations and the expansion of the 
> __MINGW_NAME_AW macro leads to name clashes.
> 


No, it is fine to have those macros before.

MSDN lists lineAddProviderW and lineAddProviderA, but not
lineAddProvider, so IMHO the proper fix is to remove non-suffixed
lineAddProvider. The non-suffixed ones will never be reached anyway if
those macros are in effect.

Kai, Ozkan, any comments?

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to