llvm dev - Dec 2009 - [LLVMdev] MinGW llvm-gcc --enable-stdcall-fixup error

When attempting to compile this simple testing tool

http://github.com/oneclick/rubyinstaller/blob/fake/resources/tools/fakeruby.c

I get the following:

C:\Users\Jon\Documents\CDev\sandbox>llvm-gcc -Wall -o fakeruby.exe fakeruby.c
Warning: resolving _GetModuleHandleA by linking to _GetModuleHandleA at 4
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
Warning: resolving _GetProcAddress by linking to _GetProcAddress at 8
Warning: resolving _GetEnvironmentVariableA by linking to
_GetEnvironmentVariableA at 12
Warning: resolving _GetCurrentProcessId by linking to _GetCurrentProcessId at 0


...OK, I'll take llvm-gcc's advice:

C:\Users\Jon\Documents\CDev\sandbox>llvm-gcc --enable-stdcall-fixup -Wall -o
fakeruby.exe fakeruby.c

cc1.exe: error: unrecognized command line option
"-fenable-stdcall-fixup"


Note that the cc1.exe error occurs regardless of -Wall's presence.

In addition to the cc1 error, is there a good reason for the initial warning
msgs screen dump?  Plain vanilla gcc (MinGW) does not dump these warnings, and
it seems unnecessary to require the use of --enable-stdcall-fixup when using
stdcall prototyped APIs.

Jon

Hello
> In addition to the cc1 error, is there a good reason for the initial
warning msgs screen dump?  Plain vanilla gcc (MinGW) does not dump these
warnings, and it seems unnecessary to require the use of --enable-stdcall-fixup
when using stdcall prototyped APIs.
Yes, this is known problem and I'm going to redo all stdcall /
fastcall mangling stuff for 2.7. This option is for the linker, so,
you have to pass it via -Wl,--enable-stdcall-fixup

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University