The -threaded option is useful even when not using any special RTS
options. At one point in time, I had problems when running running
external programs and reading their output. With the normal runtime
that would often hang, but it worked fine with the threaded
runtime. I
just started using -threaded all the time to avoid any issues like
that.
In the debian library, we do fork off some external programs such as
'tar' and 'ar' when dealing the .deb files. So it could be affected
by
that issue. However, the process stuff has been overhauled since I
saw
the issues with external processes and hanging -- so I have no idea
if
it is still an issue. I would not be surprised if it still is though.
- jeremy
On Jun 25, 2010, at 8:30 AM, Joachim Breitner wrote:
Hi David,
debian.cabal specifies
ghc-options: -O2 -threaded -W
which does not work on some architectures, as they do not have a
threaded runtime.¹ Are you sure that this option is actually useful?
IIRC it is only relevant if the binary is called with "+RTS -N -
RTS"?
We would have to make the option dependent on a Cabal flag which is
set
depending whether the threaded RTS is available on the current
architecture. But if it is not useful anyways, It’d be easier to
just
remove it.
Greetings,
Joachim
¹ https://buildd.debian.org/build.php?&stamp=1277472339&ver=3.47-3&pkg=haskell-debian&arch=sparc&act=updpkg
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata