summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorPeter Simons <simons@cryp.to>2015-12-15 22:09:37 +0100
committerPeter Simons <simons@cryp.to>2015-12-16 21:33:56 +0100
commita421e7bd4a28c69bded8b17888325e31554f61a1 (patch)
tree1229dfb657df0f6d25fdeca7afd36ef448f3a335 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parenteae27e77980bcbe4f7bcec1b2aec517d29f9630c (diff)
ghc-7.10.3: don't pass compiler or linker flags through a response file
The new GHC version contains a patch [1] that passes linker and compiler flags to GCC via response files rather than directly on the command-line. This is supposed to be beneficial on Windows and other platforms that have trouble dealing with long argument lists. On NixOS, however, this feature breaks the flag handling provided by gcc-wrapper [2] and therefore causes the entire GHC build to fail. This issue has been reported upstream at [3]. It's not clear yet how to remedy this problem, but until we've figured that out we just don't pass compiler flags in response files on NixOS to fix https://github.com/NixOS/nixpkgs/issues/10752. [1] https://github.com/ghc/ghc/commit/296bc70b5ff6c853f2782e9ec5aa47a52110345e [2] https://github.com/NixOS/nixpkgs/issues/11762 [3] https://ghc.haskell.org/trac/ghc/ticket/11147
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions