aMule 2.0.0 rc4 released www.amule.org ebuild from official forum
Created attachment 35256 [details] amule 2.0.0 rc4 ebuild
it seems that in a few days there will be an hotfix that will fix an important network bug. Maybe inclusion in portage can wait for this to exit.
Created attachment 35421 [details] amule-2.0.0_rc4-r1.ebuild hotfix released, new ebuild P.S. some utilities (webserver for example) now require wxBase but the library isn't in portage, so I can't add the dependency.
It won't compile against dev-libs/crypto++-5.2. I'll try to fix this ASAP.
Created attachment 35428 [details] amule-2.0.0_rc4-r1.ebuild for the moment =dev-libs/crypto++-5.1-r1
I've made a patch for the configure script that makes it detect the right kind of headers. Sadly though that crypto++ must have undergone changes that a-mule can't cope with because it still refuses to compile.
Created attachment 35431 [details, diff] fixe for the configure script fixes the configure script to use the right headers style
I've submitted bug report, I hope the developer will fix this ASAP. For the moment amule requires crypto++-5.1.
To fix compilation with Crypto++ 5.2, apply the following patch. However, please note that I have yet to test if aMule functions correctly with Crypto++ 5.2. Anway, the patch: --- amule-dev-cvs/src/opcodes.h 2004-07-14 18:27:58.000000000 +0200 +++ amule-crypto//src/opcodes.h 2004-07-15 21:29:17.000000000 +0200 @@ -139,7 +139,7 @@ // you shouldn't change anything here if you are not really sure, or amule will probaly not work #define MAXFRAGSIZE 1300 #define PARTSIZE 9728000 -#define BLOCKSIZE 184320 +const int BLOCKSIZE = 184320; #define OP_EDONKEYHEADER 0xE3 #define OP_EDONKEYPROT OP_EDONKEYHEADER #define OP_PACKEDPROT 0xD4
Using that patch it compiles fine, but still issues errors concerning crypto++. I'll test it later today to see if there are any flaws when running it.
*** Bug 57394 has been marked as a duplicate of this bug. ***
referring to bug #57394, it seems that amule CVS now works flawlessy with libcrypto++ 5.2 and a new rc (rc5) will be released soon, maybe today.
sorry I mean bug #57442
see bug #57528 rc5 fixes the prob