summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorProfpatsch <mail@profpatsch.de>2022-06-29 18:30:10 +0200
committerProfpatsch <mail@profpatsch.de>2022-06-30 10:12:50 +0200
commita1aed2a716ff3471f91f0ba57f551335202df98b (patch)
treeed425364cdf7cb703a675a6f75b0a5f3ee12febf /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent7f3cdfd2ba5a05a2d413c2cd9c421a4b0a28ac94 (diff)
builders/writeHaskell: build with threaded GHC runtime
Some haskell code starts silently hanging when not built with a threaded runtime, so let’s assume people using `writeHaskell` don’t care about micro-optimizations like this and do the expected thing. Some architectures don’t support a threaded runtime, for these we provide the `threadedRuntime` option to turn it off (it should fail at build time in that case, easy to detect). If somebody already passed `"-threaded"` before via ghcArgs, this will not add the flag a second time. Thus it’s backward-compatible in this regard. I tested out both branches (with `-threaded` set and not set before), on an example I had where the runtime would hang when not compiled with `-threaded`.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions