ghc-options: -threaded breaks some arches

Trent W. Buck twb at
Thu Oct 29 03:55:53 EDT 2009

Cabal developers,

Joachim Breitner <nomeata at> writes:

> Am Sonntag, den 16.08.2009, 17:47 +0100 schrieb Neil Mitchell: 
>> > trying to build hlint does not work on some architectures (at least
>> > alpha, s390, mips) where no threaded RTS is available. An example build
>> > log is available at
>> >
>> >
>> > This is caused by
>> >        ghc-options:        -fno-warn-overlapping-patterns -threaded
>> > in your hlint.cabal file.
>> > [..]
>> > If not, would it be possible to make this option dependent
>> > on the availability of a threaded RTS (either by direct support in cabal
>> > for checking it, similar to os(..) checks, or by passing a "-fthreaded"
>> > flag to setup configure)?
>> Yes, of course. What suits you? Any os checks would go wrong, so an
>> -fnothreaded flag seems sensible? I'd still like threading to be the
>> default.
> that would be a start, thanks.
> Of course I’d prefer if cabal had automatic support for this. I guess is
> does not ATM, so for now the flag is ok, and I’m hereby telling the
> Cabal people about this :-)

Did a trac ticket ever get created for this?  This affects Darcs 2.3.0,
so I'm about to add an -f-threaded to darcs.cabal for 2.4.0, because I
don't know how to tell Cabal "use -threaded iff you can".

More information about the cabal-devel mailing list