Ticket #24: setup.py.diff

setup.py

@@ -126 +126 @@
     cryptopp_src = [ os.path.join('cryptopp', x) for x in os.listdir('cryptopp') if x.endswith('.cpp') ]
     extra_srcs.extend(cryptopp_src)
 
+# So it would appear that SSE2 support is somewhat undefined on many
+# AMD-based CPU chipsets. They officially don't support some of the
+# instructions that crypto++ tries to use--which implies that crypto++ CPU
+# capability detection is currently incorrect. So, while that remains true,
+# all we can do is detect those platforms that exhibit the issue, and
+# disable the crypto++ assembly on them.
+#
+# Additionally, it's not portably possible to determine the actual CPU name
+# via platform.processor() on NetBSD (and even some Linux) because it just
+# returns the same thing as platform.machine(): i386 or x86_64 or ...
+
+arch = platform.architecture()
+syst = platform.system()
+if '32bit' in arch:
+    if 'NetBSD' in syst:
+        print "You are on 32-bit NetBSD. Disabling assembly optimisations."
+        define_macros.append(('CRYPTOPP_DISABLE_ASM', 1))
+
 # In either case, we must provide a value for CRYPTOPP_DISABLE_ASM that
 # matches the one used when Crypto++ was originally compiled. The Crypto++
 # GNUMakefile tests the assembler version and only enables assembly for