Package Details: beecrypt 4.2.1-6

Git Clone URL: (read-only, click to copy)
Package Base: beecrypt
Description: A strong and fast cryptography toolkit
Upstream URL:
Licenses: LGPL
Submitter: Allan
Maintainer: Dragonlord
Last Packager: Dragonlord
Votes: 154
Popularity: 0.000000
First Submitted: 2008-04-15 10:45
Last Updated: 2018-11-11 16:37

Latest Comments

1 2 3 Next › Last »

fucker01 commented on 2018-11-10 09:13

Gentoo already fixed the issue. See here for the bug And the patch is here

scorici commented on 2018-10-16 18:17

It does not build:

Dragonlord commented on 2014-01-29 21:22

Download works, seems like temporary issue only.

roobre commented on 2014-01-15 01:52

Download link is broken. Try:$pkgname/$pkgname/$pkgver/$pkgname-$pkgver.tar.gz

(Sry for hotlinking a mirror, but that's the only way sourceforge does not answer with an html)

Synthead commented on 2012-09-20 16:43

Please update this package so it builds; thanks!

mrbit commented on 2012-08-03 13:53

confirm work

build() {
cd ${srcdir}/$pkgname-$pkgver
./configure --prefix=/usr --sysconfdir=/etc --without-java --disable-openmp --with-python=python2

Anonymous comment on 2012-08-01 20:47

'-fpermissive' as pointed out by arum did the trick!

drankinatty commented on 2012-07-18 19:13

beecrypt needs updating to work with gcc 4.7,

../../include/beecrypt/c++/util/AbstractSet.h:59:27: error: ‘containsAll’ was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
../../include/beecrypt/c++/util/AbstractSet.h:59:27: note: declarations in dependent base ‘beecrypt::util::AbstractCollection<beecrypt::lang::Object>’ are not found by unqualified lookup


khampf commented on 2012-06-19 00:42

I can confirm the CXXFLAGS works. I'm flagging this package out of date even if the package itself isn't, the PKGBUILD needs an update anyways.

Synchronicity commented on 2012-05-21 19:09

I encountered the same problem, and it can be fixed by adding -fpermissive to the CXXFLAGS. This has to do with a documented change in gcc 4.7. This should be added to the PKGBUILD until the upstream version can build without the flag.