summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/GitPython/hardcode-git-path.patch
diff options
context:
space:
mode:
authorBjørn Forsman <bjorn.forsman@gmail.com>2015-09-04 12:29:22 +0200
committerBjørn Forsman <bjorn.forsman@gmail.com>2015-09-10 10:35:40 +0200
commit22321f2e58335cd39051c9403975b1015cfa68e0 (patch)
tree0a15a269aea5103200e6a5115454178aab55f0ee /pkgs/development/python-modules/GitPython/hardcode-git-path.patch
parent220e02506fe2ad533eec8b4381f29e52326d2982 (diff)
cudatoolkit: don't move $out/include to $out/usr_include
This effectively reverts 86c283824f76d849acbe6 ("If cuda headers are presented to nix [...]") and all the following workarounds that was added due to that commit. As far as I can tell[1] this hack isn't needed anymore. And moving includes to $out/usr_include causes pain for cudatoolkit users, so better get rid of it. In patches that did more than the $out/usr_include workaround, I only changed the line back to $out/include instead of re-generating the patches and fully removing the changed line. [1]: I build tested blender and caffe, and temporarily added recurseIntoAttrs to rPackages and haskellPackages so that nox-review could get proper coverage. However, many of the packages do not build even before this patch. I also built CUDA samples with cudatoolkit7 that ran fine.
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions