-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation Ubuntu #7
Comments
Rolled ssdeep back to version 2.10 then installed pydeep via pip. - Errors the same but completes install and seems to be useble.
|
@kevthehermit thanks for posting this issue. DetailThis issue is very specific to ssdeep-2.11. Previous versions of ssdeep used to build static and shared libraries. ssdeep-2.11 only builds static libraries. pydeep was not able to find the shared library when building. Avoid reverting to ssdeep-2.10Reverting back to ssdeep-2.10 should be avoided. ssdeep-2.10 had a bug in the signature generation code. If you have to revert, I recommend using ssdeep-2.9 instead. WorkaroundTill ssdeep-2.11 source is updated, you can try this workaround (from Jesse). In ssdeep-2.11/Makefile.am, remove the '-static' flag from libfuzzy_la_LDFLAGS in :
After that, run:
Then do
After that, proceed building and installing pydeep as usual. I will leave this issue open till there is an update to ssdeep. |
Thank you for the continued support of this project :) Have you considered travis for automated testing - http://docs.travis-ci.com/user/getting-started/ a sample for ssdeep on the viper project - https://github.com/botherder/viper/blob/master/.travis.yml |
Fixedssdeep-2.11.1 was released last night. It now builds shared libraries. Please update to it. I will surely look into travis-ci. Thanks! |
…ssue. Was causing an issue for pydeep (kbandla/pydeep#7)
Ubuntu Server 14.04
OS - Ubuntu 14.04 Server
Install SSDeep from source
Install from GitHub
The text was updated successfully, but these errors were encountered: