Sigbjorn Finne wrote:
Not sure what 2) refers to, but 1) and 3) is already in 6.2.x;
no need to use the heavier-weight -threaded stuff to enable
it.
What I mean is a Windows version of Simon M's:
http://www.haskell.org//pipermail/libraries/attachments/20040317/609414e2/Process-0001.obj
or al
In the current implementation of the ghc-pkg util
it is impossible to build GHCi libs if you don't have
ld in the current search path. Under Windows the
compiler usually comes with its own linker
(ghc-lib/ld.exe). Why doesn't ghc-pkg use the own
linker? If there isn't any reason not to do that
Not sure what 2) refers to, but 1) and 3) is already in 6.2.x;
no need to use the heavier-weight -threaded stuff to enable
it.
--sigbjorn
- Original Message -
From: "George Russell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 04, 2004 03:42
Subject: Windows & ghc6.04
Is there any chance that GHC 6.04, or any GHC version in the next few
months, will support the following on Windows:
1) use of native threads so that the world won't be stopped every time
you wait for a character;
Should already be in 6.02.1 - add the -threaded flag when linking, and
you'll get th
Is there any chance that GHC 6.04, or any GHC version in the next few
months, will support the following on Windows:
1) use of native threads so that the world won't be stopped every time
you wait for a character;
2) the new system-independent runProcess interface;
3) Network.Socket. (Maybe it doe
