Search Criteria
Package Details: notbit-git r342.faf0930-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/notbit-git.git (read-only, click to copy) |
|---|---|
| Package Base: | notbit-git |
| Description: | A minimal Bitmessage client |
| Upstream URL: | https://github.com/bpeel/notbit |
| Licenses: | MIT |
| Provides: | notbit |
| Submitter: | alphazo |
| Maintainer: | None |
| Last Packager: | alphazo |
| Votes: | 6 |
| Popularity: | 0.000000 |
| First Submitted: | 2013-12-11 20:21 (UTC) |
| Last Updated: | 2015-06-10 14:54 (UTC) |
Dependencies (2)
- openssl (openssl-gitAUR, openssl-aegisAUR, openssl-staticAUR, openssl-staticAUR, openssl-staticAUR, openssl-staticAUR, openssl-staticAUR, openssl-staticAUR)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
Latest Comments
Tio commented on 2020-04-11 15:36 (UTC)
Yes it fails in 2020:
deathsbreed commented on 2018-12-16 11:29 (UTC) (edited on 2018-12-16 11:30 (UTC) by deathsbreed)
The reason it fails is because although the code base is programmed for openssl v1.0, it was most likely developed in an environment where openssl v1.1 wasn't available yet[0]. Firstly, change the
openssldependency toopenssl-1.0, secondly add theCFLAGS=-I/usr/include/openssl-1.0flag to the./configurecommand. With this you shouldn't get compiler errors, but you still get a linker error, and I'm not familiar enough with the GNU autotools to fix this. The ideal would be to get autotools to compile with/usr/lib/libcrypto.so.1.0.0and/usr/lib/libssl.so.1.0.0.[0] https://github.com/bpeel/notbit/issues/14
dreieck commented on 2018-05-02 09:52 (UTC)
Fails to build for me:
alphazo commented on 2014-05-27 12:40 (UTC)
npouillard commented on 2014-04-18 12:34 (UTC)
bobberb commented on 2014-03-24 19:15 (UTC)