aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 ... 7 8 [9] 10

Author Topic: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary  (Read 272882 times)

gtoso

  • Official MacOSX Packager
  • Full Member
  • ***
  • Karma: 24
  • Offline Offline
  • Posts: 206

I can`t download those without knowing a login and password for your website. Do you expect me to use the login and password from this forum for your site?

No, this site is temporarily closed.
But yesterday I updated all 2.2.5 and last SVN links.
So what you want download? old versions?

I have temporary hosting problems  :(

For 2.2.5 Tiger/Leopard go here:
http://www.amule.org/files/details.php?file=188

I updated the links for 2.2.5 builds in my first post.

Logged

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite

Hi gtoso,

I currently use your 2.5 version but it often crashes. I attached one of the crash-log... I think it's enough since it always crashes with the same errors...

Bye
Mirko
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795

Interesting but not good enough. Would be good to know if anything is in the aMule log files.
Logged

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite

Upgraded crypto++ from 5.5.2 to 5.6.0.

Hi gtoso,
did you managed to compile aMule with "self-compiled" Crypto++ 5.6?

I was able to compile Crypto++ (not universal binary) but when I compile aMule and it come Crypto++ turn I get:
Code: [Select]
Undefined symbols:
  "CryptoPP::AlgorithmParameters::AlgorithmParameters()", referenced from:
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<char const*>(char const*, char const* const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<int const*>(char const*, int const* const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<CryptoPP::ConstByteArrayParameter>(char const*, CryptoPP::ConstByteArrayParameter const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<bool>(char const*, bool const&, bool)in amuled-ClientCreditsList.o
  "non-virtual thunk to CryptoPP::DES_EDE3::Base::ProcessAndXorBlock(unsigned char const*, unsigned char const*, unsigned char*) const", referenced from:
      vtable for CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
      vtable for CryptoPP::ClonableImpl<CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
  "CryptoPP::BlockTransformation::AdvancedProcessBlocks(unsigned char const*, unsigned char const*, unsigned char*, unsigned long, unsigned int) const", referenced from:
      vtable for CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
      vtable for CryptoPP::ClonableImpl<CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
      vtable for CryptoPP::BlockCipherImpl<CryptoPP::DES_EDE3_Info, CryptoPP::BlockCipher>in amuled-ClientCreditsList.o
      vtable for CryptoPP::AlgorithmImpl<CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> >, CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> > >in amuled-ClientCreditsList.o
      vtable for CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> >in amuled-ClientCreditsList.o
      vtable for CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>in amuled-ClientCreditsList.o
      vtable for CryptoPP::BlockCipherin amuled-ClientCreditsList.o
  "vtable for CryptoPP::AlgorithmParametersTemplate<CryptoPP::ConstByteArrayParameter>", referenced from:
      __ZTVN8CryptoPP27AlgorithmParametersTemplateINS_23ConstByteArrayParameterEEE$non_lazy_ptr in amuled-ClientCreditsList.o
  "CryptoPP::DEFAULT_CHANNEL", referenced from:
      __ZN8CryptoPP15DEFAULT_CHANNELE$non_lazy_ptr in amuled-ClientCreditsList.o
  "CryptoPP::BlockTransformation::OptimalDataAlignment() const", referenced from:
      vtable for CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
      vtable for CryptoPP::ClonableImpl<CryptoPP::BlockCipherFinal<(CryptoPP::CipherDir)0, CryptoPP::DES_EDE3::Base>, CryptoPP::DES_EDE3::Base>in amuled-ClientCreditsList.o
      vtable for CryptoPP::BlockCipherImpl<CryptoPP::DES_EDE3_Info, CryptoPP::BlockCipher>in amuled-ClientCreditsList.o
      vtable for CryptoPP::AlgorithmImpl<CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> >, CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> > >in amuled-ClientCreditsList.o
      vtable for CryptoPP::SimpleKeyingInterfaceImpl<CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>, CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info> >in amuled-ClientCreditsList.o
      vtable for CryptoPP::TwoBases<CryptoPP::BlockCipher, CryptoPP::DES_EDE3_Info>in amuled-ClientCreditsList.o
      vtable for CryptoPP::BlockCipherin amuled-ClientCreditsList.o
  "CryptoPP::AlgorithmParameters::AlgorithmParameters(CryptoPP::AlgorithmParameters const&)", referenced from:
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<char const*>(char const*, char const* const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<int const*>(char const*, int const* const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<CryptoPP::ConstByteArrayParameter>(char const*, CryptoPP::ConstByteArrayParameter const&, bool)in amuled-ClientCreditsList.o
      CryptoPP::AlgorithmParameters CryptoPP::MakeParameters<bool>(char const*, bool const&, bool)in amuled-ClientCreditsList.o
  "vtable for CryptoPP::AlgorithmParametersTemplate<bool>", referenced from:
      __ZTVN8CryptoPP27AlgorithmParametersTemplateIbEE$non_lazy_ptr in amuled-ClientCreditsList.o
  "vtable for CryptoPP::AlgorithmParametersTemplate<int>", referenced from:
      __ZTVN8CryptoPP27AlgorithmParametersTemplateIiEE$non_lazy_ptr in amuled-ClientCreditsList.o
  "vtable for CryptoPP::AlgorithmParameters", referenced from:
      __ZTVN8CryptoPP19AlgorithmParametersE$non_lazy_ptr in amuled-ClientCreditsList.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[3]: *** [amuled] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I take a look to http://gtoso.tor.it/pub/amule/osx/2.2.5/OSXBuild/amule-uni.OSXBuild but you used --with-crypto-prefix=$MACPORTS there (with $MACPORTS=/opt/local)...

UPDATE: The problem is not related to Crypto++ 5.6 since it takes place with librcryptopp portfile too... it's strange since I always compile aMule with it and it never failed before. The only thing I changed is the compiler, from gcc-4.0 to gcc-4.2.... do you experienced problems with it? I should have paid attention to the config output: crypto++ 5.6.0 (installed, in /usr/local/cryptopp/). It seems to recognize libcryptopp by itself even if I appended --with-crypto-prefix=/opt/local. I had to remove /usr/local/cryptopp/ and /usr/include/cryptopp to build aMule with Crypto++  by MacPorts.
« Last Edit: August 27, 2009, 04:28:58 PM by mirko.g »
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685

It seems to recognize libcryptopp by itself even if I appended --with-crypto-prefix=/opt/local.

Adding --with-crypto-prefix=/opt/local means configure will search for cryptlib.h in the following directories:
  • /opt/local/
  • /opt/local/include/cryptopp/
  • /opt/local/include/crypto++/
If cryptlib.h resides in another location, such as in /opt/local/cryptopp/, you should use --with-crypto-prefix=/opt/local/cryptopp.
Logged
concordia cum veritate

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite

It seems to recognize libcryptopp by itself even if I appended --with-crypto-prefix=/opt/local.

Adding --with-crypto-prefix=/opt/local means configure will search for cryptlib.h in the following directories:
  • /opt/local/
  • /opt/local/include/cryptopp/
  • /opt/local/include/crypto++/
If cryptlib.h resides in another location, such as in /opt/local/cryptopp/, you should use --with-crypto-prefix=/opt/local/cryptopp.

Yes I know... or, I knew! But I don't know how it found it in /usr/local/...
Logged

Vollstrecker

  • Administrator
  • Hero Member
  • *****
  • Karma: 67
  • Offline Offline
  • Posts: 1549
  • Unofficial Debian Packager
    • http://vollstreckernet.de

Sure you know. Either, if you use configure, it prints it. Or if you look at the compile commands, you'll see which path's are included. If both fail, ldd is your friend.
Logged
Homefucking is killing prostitution

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685

Yes I know... or, I knew! But I don't know how it found it in /usr/local/...

Because it automatically checks the following prefixes (in this order):
  • the path given with --with-crypto-prefix
  • /usr
  • /usr/local
  • /opt
  • /opt/local
  • /usr/pkg
  • /mingw

First found is used.
Logged
concordia cum veritate

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite

Because it automatically checks the following prefixes (in this order):
  • the path given with --with-crypto-prefix
  • /usr

First found is used.

Are you sure? Far from me to doubt your words... but I really did set --with-crypto-prefix=/opt/local and it continued taking /usr/local/cryptopp until I removed /usr/include/cryptopp...  ???
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #129 on: September 15, 2009, 10:48:28 PM »

Starting from rev. 9803 if you set a search path with --with-crypto-prefix the system paths are not scanned. This is to prevent finding an unwanted Crypto++ installation.
Logged
concordia cum veritate

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #130 on: September 16, 2009, 10:04:43 AM »

Starting from rev. 9803 if you set a search path with --with-crypto-prefix the system paths are not scanned. This is to prevent finding an unwanted Crypto++ installation.

Does it take place with libiconv too?  ???
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #131 on: September 16, 2009, 10:39:53 AM »

No, that's out of scope.
Logged
concordia cum veritate

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #132 on: February 04, 2011, 08:43:53 AM »

I've just bought my first Intel Mac and Snow Leopard, and wish to update my current aMule 2.2.2 which I was using on a PPC Mac with Tiger, which has always been stable and worked perfectly for me. Please could someone recommend whether I should stick with this version or which more recent stable version I should download. Please note that I am a rather unsophisticated user of this application and talk of compiling, tar, bz  and other technical aspects do not mean anything to me. Many thanks.
Logged

littleb2005

  • Approved Newbie
  • *
  • Karma: 2
  • Offline Offline
  • Posts: 32
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #133 on: February 05, 2011, 12:43:22 AM »

I've just bought my first Intel Mac and Snow Leopard, and wish to update my current aMule 2.2.2 which I was using on a PPC Mac with Tiger, which has always been stable and worked perfectly for me. Please could someone recommend whether I should stick with this version or which more recent stable version I should download. Please note that I am a rather unsophisticated user of this application and talk of compiling, tar, bz  and other technical aspects do not mean anything to me. Many thanks.


i am not sure you get support for such an old version of amule also if compile not your thing then look for ones that have already been compile and built


the new most stable version is 2.2.6

http://sourceforge.net/projects/amule/files/aMule/2.2.6/aMuleCore-2.2.6-x86-Leopard-MFb03.dmg/download

or if u want to run an svn build which should contains more fixes and may be stable then go here

http://forum.amule.org/index.php?topic=18474.0

Logged

ngllgn

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: aMule 2.2.x and SVN (with amuled e amulegui) Tiger/Leopard Universal Binary
« Reply #134 on: February 26, 2011, 02:37:06 PM »

OK. I've downloaded aMule 2.2.6 and

1 Added aMule to applications in System Preferences/Security Settingss/Firewall using the + button after deleting the settings for aMule 2.2.5
2 In aMule/Preferences/Connection set the Standard client TCP and UDP and the extended server requests (TCP+3) Ports
3 Checked Enable UPnP TCP Port (with the same port number as the Standard client TCP Port
4 Gone into my router on 192.168.1.1 and set
a) NAT - Virtual Servers Setup and set the same Port numbers as 2 above (with the only doubt being whether the Server IP address should be the router address ie 192.168.1.1 or the computer's address ie 192.168.1.11 (help please?)
b) NAT - port forwarding with the same External Port Start and End numbers for both TCP and UDP protocols as 2 above
c) NAT - port triggering with the same Trigger and Open Protocol and Port Range numbers as 2 above

I am still getting a Low-ID, firewalled KAD and a Universal Plug and Play error which reads like this:


2011-02-26 14:28:53: Universal Plug and Play: error(UPNP_DISCOVERY_ADVERTISEMENT_ALIVE): Error retrieving device description from http://192.168.1.1:5431/dyndev/uuid:0000e098-c0a0-00e0-b0a0-48b8003808e0: UPNP_E_INVALID_DESC.

I am at a loss as to what to do next. I had the same problem years ago when first installing a much earlier version of aMule on the old PPC G5 iMac, but cannot remember how I solved it. I have a feeling it just solved itself after weeks of frustration and my doing nothing. But is there nothing I can do to be a bit more proactive this time? Grateful for any advice offered. Thanks.
Logged
Pages: 1 ... 7 8 [9] 10