-
Notifications
You must be signed in to change notification settings - Fork 561
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
Building on Ubuntu 16.04 LTS #126
Comments
On the way to make 16.04 LTS a supported platform, here are some install info.
From there, Note: good tutorial is here: https://github.com/BVLC/caffe/wiki/GeForce-GTX-1080,---CUDA-8.0,---Ubuntu-16.04,---Caffe |
require packages autoconf and libtool-bin to build curlcpp from sources on ubuntu 16.04 LTS |
quick info: The bug reported by http://stackoverflow.com/questions/33420631/link-errors-with-curlpp is now fixed by version 0.7.4 on cURLpp's official github repository: https://github.com/jpbarrette/curlpp. I hope that ubuntu will update their package to include new versions. |
@jpbarrette thanks for the heads up! |
based on 0.8.0 version, the step is: |
Here is how you fix the curlpp problem on Ubuntu 16.04:
|
Had same error, thanks for provided solution @MartinThoma. I think this should be in DD |
Your note is very useful! Thank you very much! |
Thank you so much, guys!! |
By the way we have scripted the install of deepdetect for ubuntu 16.04 here: https://github.com/soprasteria/cybersecurity-dfm/blob/master/install_ubuntu.sh#L245 |
This is the placeholder for information regarding the building of deepdetect on Ubuntu 16.04 LTS (expected future reference platform).
Build status: successful, tested with Caffe back-end on CPU
Thanks to @MartinThoma the correct way of doing it is below:
Existing difficulties with 15.10 (#29) appear to have been fixed, but for the version ofcurlpp
that is still broken (http://stackoverflow.com/questions/33420631/link-errors-with-curlpp). The fix remains to rebuild curlpp from https://github.com/datacratic/curlpp:EDIT: fixed.
The text was updated successfully, but these errors were encountered: