From 84323ac9799498960f2075110349f8b05d5465fc Mon Sep 17 00:00:00 2001
From: Peter Simons <simons@cryp.to>
Date: Tue, 27 Jul 2010 23:50:51 +0000
Subject: [PATCH] pycryptopp: use the embedded crypto++ library when compiling
this module
crypto++ has an impurity that leads to test suite failures in this
module, i.e. in sha256. When that impurity has been fixed, we should try
building on top of the the pristine crypto++ library again.
svn path=/nixpkgs/trunk/; revision=22760
---
pkgs/top-level/python-packages.nix | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pkgs/top-level/python-packages.nix b/pkgs/top-level/python-packages.nix
index d1459db03ce..0a48f32c60f 100644
--- a/pkgs/top-level/python-packages.nix
+++ b/pkgs/top-level/python-packages.nix
@@ -516,9 +516,9 @@ rec {
};
# Use our own copy of Crypto++.
- preConfigure = "export PYCRYPTOPP_DISABLE_EMBEDDED_CRYPTOPP=1";
+ # preConfigure = "export PYCRYPTOPP_DISABLE_EMBEDDED_CRYPTOPP=1";
- buildInputs = [ setuptoolsDarcs darcsver pkgs.cryptopp ];
+ buildInputs = [ setuptoolsDarcs darcsver /* pkgs.cryptopp */ ];
meta = {
homepage = http://allmydata.org/trac/pycryptopp;