From: SourceForge.net <no...@so...> - 2008-06-07 12:05:08
|
Bugs item #1987329, was opened at 2008-06-07 15:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1987329&group_id=2435 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: gcc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alex Yaroslavsky (yaroslavsky_a) Assigned to: Nobody/Anonymous (nobody) Summary: --enable-stdcall-fixup wrong command line usage Initial Comment: I am using the latest gcc 4.3.0 alpha from your site with all the latest mingw components. gcc version 4.3.0 20080305 (alpha-testing) mingw-20080502 (GCC) GNU ld (GNU Binutils) 2.18.50.20080109 When compiling one of my projects I got the following warnings: Warning: resolving non-virtual thunk to CArchiveUpdateCallback::AddRef()@4 by linking to non-virtual thunk to CArchiveUpdateCallback::AddRef() Use --enable-stdcall-fixup to disable these warnings Use --disable-stdcall-fixup to disable these fixups So I then added --enable-stdcall-fixup to g++ arguments, this gave me errors that some preprocessor didn't know what -fenable-stdcall-fixup was and build failed. So I then added --enable-stdcall-fixup as an argument to ld, ld ignored it. Then I changed it to -enable-stdcall-fixup (only one dash) and it worked. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1987329&group_id=2435 |