Linking hsc2hs .c output on Windows w/ build system: is it just me..?

[Sigbjorn Finne]

Simon Marlow wrote:
> On 29/04/2009 01:23, Sigbjorn Finne wrote:
>> Thanks Simon,
>>
>> sorry for not noticing your reply amidst the flow of g-h-b ticket 
>> reports
>> before now. As there is no need to sail that close to the wind of
>> playing with the delicate linking & loading orders of the CRT and
>> base DLLs like kernel32, my suggestion would be simply to avoid
>> it. You don't do any explicit "-lgcc -lc" trickery when invoking gcc/ld
>> on other platforms, so why be different?
>>
>> Apart from the changes to Win32.cabal and base.cabal mentioned
>> in the original e-mail, injecting addDLL() calls for kernel32 and
>> msvcrt in initLinker() ought to do it.
>
> I've now done exactly that.  This seems like a good fix to try to get 
> into 6.10.4 - can you think of any unexpected consequences?
>
Cool, given that the RTS already has those two DLLs loaded & repeated 
addDLL()s
is fine (i.e., if other packages contain e.g., "kernel32" uses), I can't 
think of any...other
than possibly more contribs from people building on Windows ;-)

If you feel the risk is not worth taking for 6.10.4, I'm totally fine 
with pushing it out.

thanks,
--sigbjorn