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

[Sigbjorn Finne]

Oh, and a simple test case:

foo$ cat a.c
int main() { return 0; }
foo$ c:/ghc/ghc-6.10.1/gcc -o a a.c
foo$ ./a ; echo $?
0
foo$ c:/ghc/ghc-6.10.1/gcc -o a a.c -lkernel32
foo$ ./a ; echo $?
0
foo$ c:/ghc/ghc-6.10.1/gcc -o a a.c -lkernel32 -lmsvcrt
foo$ ./a ; echo $?
<crash-reporting dialog box shows up>
5
foo$

--sigbjorn

On 4/25/2009 11:38, Sigbjorn Finne wrote:
> On 4/25/2009 05:37, Ian Lynagh wrote:
>> Hi Sigbjorn,
>>
>> On Fri, Apr 24, 2009 at 03:04:14PM -0700, Sigbjorn Finne wrote:
>>  
>>> I've been experiencing repeated woes over the past 4-5 months
>>> when trying to spin up build trees on Windows with the new build
>>> system.
>>>     
>>
>> By "new build system" do you mean
>>     http://darcs.haskell.org/ghc-new-build-system/
>> ?
>>   
> Hi Ian,
>
> young and old. The above one + ones using the older (git & darcs 
> versions)
>
>>> The problem is that hsc2hs generated .c files (Foo_hsc_make.c) when
>>> compiled and linked via the 'ghc' that's configured against, will 
>>> produce
>>> .exe's that crashes right out of the gates.
>>>     
>>
>> Do you mean that building GHC fails, or that building other things using
>> the built GHC fails? If the latter, can you give a testcase please?
>>
>>
>>   
> Right, when building the repo contents. Any .hsc that's in the tree 
> elicits a hard crash (i.e.,
> dialog box pops up reporting the failure of any *_hsc_make.exe ) This 
> is when building with
> 6.10.1, but that's not the real cause here.
>
> If I don't take the evasive action (as outlined in the original 
> e-mail), the resulting stage1/stage2
> ghc installs will fail also (provided I've manually guided the build 
> process past these crashes
> to reach completion first, of course.)
>
> hth
> --sigbjorn
>
> _______________________________________________
> Glasgow-haskell-bugs mailing list
> Glasgow-haskell-bugs at haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs