[tahoe-lafs-trac-stream] [pycryptopp] #100: upgrade python bindings to use a recent stable version of cryptopp
pycryptopp
trac at tahoe-lafs.org
Sat Jul 2 12:44:15 UTC 2016
#100: upgrade python bindings to use a recent stable version of cryptopp
------------------------+------------------------
Reporter: dawuud | Owner: dawuud
Type: enhancement | Status: new
Priority: blocker | Milestone:
Version: 0.5.29 | Resolution:
Keywords: | Launchpad Bug:
------------------------+------------------------
Comment (by dawuud):
using the cryptopp maintainer's git repo
git at github.com:weidai11/cryptopp.git
copied sources files from tagged branch CRYPTOPP_5_6_3;
however pycryptopp doesn't build because of errors like these
{{{
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-DCRYPTOPP_DISABLE_ASM=1 -I. -I/usr/include/python2.7 -c src-
cryptopp/casts.cpp -o build/temp.linux-x86_64-2.7/src-cryptopp/casts.o -w
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for
C/ObjC but not for C++
In file included from src-cryptopp/seckey.h:16:0,
from src-cryptopp/cast.h:9,
from src-cryptopp/casts.cpp:2:
src-cryptopp/cryptlib.h: In member function ‘virtual void
CryptoPP::SimpleKeyingInterface::Resynchronize(const byte*, int)’:
src-cryptopp/cryptlib.h:593:21: error: ‘CRYPTOPP_UNUSED’ was not declared
in this scope
CRYPTOPP_UNUSED(iv); CRYPTOPP_UNUSED(ivLength);
^
src-cryptopp/cryptlib.h: In member function ‘void
CryptoPP::SimpleKeyingInterface::AssertValidKeyLength(size_t) const’:
src-cryptopp/cryptlib.h:655:26: error: ‘CRYPTOPP_UNUSED’ was not declared
in this scope
{CRYPTOPP_UNUSED(length); assert(IsValidKeyLength(length));}
^
}}}
--
Ticket URL: <https://tahoe-lafs.org/trac/pycryptopp/ticket/100#comment:3>
pycryptopp <https://Tahoe-LAFS.org/trac/pycryptopp>
python bindings to the (C++) "Crypto++" library
More information about the tahoe-lafs-trac-stream
mailing list