aMule Forum

English => aMule Help => Topic started by: kriztofo on May 13, 2004, 06:54:18 AM

Title: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: kriztofo on May 13, 2004, 06:54:18 AM
RC3 fails to compile under GCC 3.4 on the crypto stuff seemingly because of the major template changes in g++ (maybe someday there will be a 100% c++ compiler).

I'm not too knowledgeable so i tried to recompile libcrypto but that fails to compile as well with GCC 3.4.

Everything compiled fine with GCC 3.2.3

*edit*
oh yeah and RC2 gives the same errors

Begin dump
--------------------------------------------------
In file included from /usr/include/cryptopp/filters.h:4,
                 from /usr/include/cryptopp/pubkey.h:36,
                 from /usr/include/cryptopp/pkcspad.h:5,
                 from /usr/include/cryptopp/rsa.h:9,
                 from ClientCredits.h:32,
                 from BaseClient.cpp:47:
/usr/include/cryptopp/simple.h: In member function `bool CryptoPP::Unflushable::Flush(bool, int, bool)':
/usr/include/cryptopp/simple.h:71: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h:71: error: (Each undeclared identifier is reported only once for each function it appears in.)
/usr/include/cryptopp/simple.h: In member function `bool CryptoPP::Unflushable::ChannelFlush(const std::string&, bool, int, bool)':
/usr/include/cryptopp/simple.h:80: error: there are no arguments to `AttachedTransformation' that depend on a template parameter, so a declaration of `AttachedTransformation' must be available
/usr/include/cryptopp/simple.h:80: error: (if you use `-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
/usr/include/cryptopp/simple.h: In member function `void CryptoPP::Multichannel::Initialize(const CryptoPP::NameValuePairs&, int)':
/usr/include/cryptopp/simple.h:134: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h: In member function `bool CryptoPP::Multichannel::Flush(bool, int, bool)':
/usr/include/cryptopp/simple.h:136: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h: In member function `bool CryptoPP::Multichannel::MessageSeriesEnd(int, bool)':
/usr/include/cryptopp/simple.h:138: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h:138: error: there are no arguments to `ChannelMessageSeriesEnd' that depend on a template parameter, so a declaration of `ChannelMessageSeriesEnd' must be available
/usr/include/cryptopp/simple.h: In member function `unsigned char* CryptoPP::Multichannel::CreatePutSpace(unsigned int&)':
/usr/include/cryptopp/simple.h:140: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h: In member function `unsigned int CryptoPP::Multichannel::Put2(const unsigned char*, unsigned int, int, bool)':
/usr/include/cryptopp/simple.h:142: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h: In member function `unsigned int CryptoPP::Multichannel::PutModifiable2(unsigned char*, unsigned int, int, bool)':
/usr/include/cryptopp/simple.h:144: error: `NULL_CHANNEL' undeclared (first use this function)
/usr/include/cryptopp/simple.h: In member function `bool CryptoPP::Multichannel::ChannelPutModifiable(const std::string&, unsigned char*, unsigned int)':
/usr/include/cryptopp/simple.h:151: error: there are no arguments to `ChannelPut' that depend on a template parameter, so a declaration of `ChannelPut' must be available
In file included from /usr/include/cryptopp/filters.h:7,
                 from /usr/include/cryptopp/pubkey.h:36,
                 from /usr/include/cryptopp/pkcspad.h:5,
                 from /usr/include/cryptopp/rsa.h:9,
                 from ClientCredits.h:32,
                 from BaseClient.cpp:47:
/usr/include/cryptopp/smartptr.h: In member function `bool CryptoPP::value_ptr::operator==(const CryptoPP::value_ptr&)':
/usr/include/cryptopp/smartptr.h:57: error: `m_p' undeclared (first use this function)
/usr/include/cryptopp/smartptr.h: In member function `CryptoPP::value_ptr& CryptoPP::value_ptr::operator=(const CryptoPP::value_ptr&)':
/usr/include/cryptopp/smartptr.h:63: error: `m_p' undeclared (first use this function)
/usr/include/cryptopp/smartptr.h: In member function `CryptoPP::clonable_ptr& CryptoPP::clonable_ptr::operator=(const CryptoPP::clonable_ptr&)':
/usr/include/cryptopp/smartptr.h:84: error: `m_p' undeclared (first use this function)
In file included from /usr/include/cryptopp/pkcspad.h:5,
                 from /usr/include/cryptopp/rsa.h:9,
                 from ClientCredits.h:32,
                 from BaseClient.cpp:47:
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_CryptoSystemBase::FixedMaxPlaintextLength() const':
/usr/include/cryptopp/pubkey.h:145: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_CryptoSystemBase::FixedCiphertextLength() const':
/usr/include/cryptopp/pubkey.h:146: error: there are no arguments to `GetTrapdoorFunctionBounds' that depend on a template parameter, so a declaration of `GetTrapdoorFunctionBounds' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_CryptoSystemBase::PaddedBlockBitLength() const':
/usr/include/cryptopp/pubkey.h:150: error: there are no arguments to `GetTrapdoorFunctionBounds' that depend on a template parameter, so a declaration of `GetTrapdoorFunctionBounds' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::HashTransformation& CryptoPP::PK_MessageAccumulatorImpl::AccessHash()':
/usr/include/cryptopp/pubkey.h:291: error: `m_object' undeclared (first use this function)
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_SignatureSchemeBase::SignatureLength() const':
/usr/include/cryptopp/pubkey.h:300: error: there are no arguments to `GetTrapdoorFunctionBounds' that depend on a template parameter, so a declaration of `GetTrapdoorFunctionBounds' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_SignatureSchemeBase::MaxRecoverableLength() const':
/usr/include/cryptopp/pubkey.h:302: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `bool CryptoPP::TF_SignatureSchemeBase::IsProbabilistic() const':
/usr/include/cryptopp/pubkey.h:307: error: there are no arguments to `GetTrapdoorFunctionInterface' that depend on a template parameter, so a declaration of `GetTrapdoorFunctionInterface' must be available
/usr/include/cryptopp/pubkey.h:307: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `bool CryptoPP::TF_SignatureSchemeBase::AllowNonrecoverablePart() const':
/usr/include/cryptopp/pubkey.h:309: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `bool CryptoPP::TF_SignatureSchemeBase::RecoverablePartFirst() const':
/usr/include/cryptopp/pubkey.h:311: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::TF_SignatureSchemeBase::MessageRepresentativeBitLength() const':
/usr/include/cryptopp/pubkey.h:315: error: there are no arguments to `GetTrapdoorFunctionBounds' that depend on a template parameter, so a declaration of `GetTrapdoorFunctionBounds' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::HashIdentifier CryptoPP::TF_ObjectImplBase::GetHashIdentifier() const':
/usr/include/cryptopp/pubkey.h:404: error: non-template `HashIdentifierLookup2' used as template
/usr/include/cryptopp/pubkey.h:404: error: (use `typename SCHEME_OPTIONS::MessageEncodingMethod::HashIdentifierLookup::template HashIdentifierLookup2' to indicate that it is a template)
/usr/include/cryptopp/pubkey.h:404: error: declaration does not declare anything
/usr/include/cryptopp/pubkey.h:405: error: `L' has not been declared
/usr/include/cryptopp/pubkey.h:405: error: there are no arguments to `Lookup' that depend on a template parameter, so a declaration of `Lookup' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::TF_PublicObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PublicKey&) const':
/usr/include/cryptopp/pubkey.h:449: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::TF_PrivateObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PrivateKey&) const':
/usr/include/cryptopp/pubkey.h:457: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::TF_PrivateObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PublicKey&) const':
/usr/include/cryptopp/pubkey.h:458: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `bool CryptoPP::DL_PublicKey::GetVoidValue(const char*, const std::type_info&, void*) const':
/usr/include/cryptopp/pubkey.h:677: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `virtual const T& CryptoPP::DL_PublicKey::GetPublicElement() const':
/usr/include/cryptopp/pubkey.h:684: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `virtual void CryptoPP::DL_PublicKey::SetPublicElement(const T&)':
/usr/include/cryptopp/pubkey.h:685: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `virtual T CryptoPP::DL_PublicKey::ExponentiatePublicElement(const CryptoPP::Integer&) const':
/usr/include/cryptopp/pubkey.h:688: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `virtual T CryptoPP::DL_PublicKey::CascadeExponentiateBaseAndPublicElement(const CryptoPP::Integer&, const CryptoPP::Integer&) const':
/usr/include/cryptopp/pubkey.h:693: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::DL_PrivateKey::MakePublicKey(CryptoPP::DL_PublicKey&) const':
/usr/include/cryptopp/pubkey.h:712: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h:713: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
(...)
/usr/include/cryptopp/pubkey.h:1117: error: there are no arguments to `GetKeyInterface' that depend on a template parameter, so a declaration of `GetKeyInterface' must be available
/usr/include/cryptopp/pubkey.h:1119: error: there are no arguments to `MessageRepresentativeLength' that depend on a template parameter, so a declaration of `MessageRepresentativeLength' must be available
/usr/include/cryptopp/pubkey.h:1120: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h:1121: error: there are no arguments to `GetHashIdentifier' that depend on a template parameter, so a declaration of `GetHashIdentifier' must be available
/usr/include/cryptopp/pubkey.h:1122: error: there are no arguments to `MessageRepresentativeBitLength' that depend on a template parameter, so a declaration of `MessageRepresentativeBitLength' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::DecodingResult CryptoPP::DL_VerifierBase::RecoverAndRestart(unsigned char*, CryptoPP::PK_MessageAccumulator&) const':
/usr/include/cryptopp/pubkey.h:1132: error: there are no arguments to `GetMaterial' that depend on a template parameter, so a declaration of `GetMaterial' must be available
/usr/include/cryptopp/pubkey.h:1135: error: there are no arguments to `GetSignatureAlgorithm' that depend on a template parameter, so a declaration of `GetSignatureAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1136: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h:1137: error: there are no arguments to `GetKeyInterface' that depend on a template parameter, so a declaration of `GetKeyInterface' must be available
/usr/include/cryptopp/pubkey.h:1139: error: there are no arguments to `MessageRepresentativeLength' that depend on a template parameter, so a declaration of `MessageRepresentativeLength' must be available
/usr/include/cryptopp/pubkey.h:1140: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h:1143: error: there are no arguments to `GetHashIdentifier' that depend on a template parameter, so a declaration of `GetHashIdentifier' must be available
/usr/include/cryptopp/pubkey.h:1144: error: there are no arguments to `MessageRepresentativeBitLength' that depend on a template parameter, so a declaration of `MessageRepresentativeBitLength' must be available
/usr/include/cryptopp/pubkey.h:1152: error: there are no arguments to `GetMessageEncodingInterface' that depend on a template parameter, so a declaration of `GetMessageEncodingInterface' must be available
/usr/include/cryptopp/pubkey.h:1153: error: there are no arguments to `GetHashIdentifier' that depend on a template parameter, so a declaration of `GetHashIdentifier' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::DL_CryptoSystemBase::MaxPlaintextLength(unsigned int) const':
/usr/include/cryptopp/pubkey.h:1169: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `unsigned int CryptoPP::DL_CryptoSystemBase::CiphertextLength(unsigned int) const':
/usr/include/cryptopp/pubkey.h:1176: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::DecodingResult CryptoPP::DL_DecryptorBase::Decrypt(CryptoPP::RandomNumberGenerator&, const unsigned char*, unsigned int, unsigned char*) const':
/usr/include/cryptopp/pubkey.h:1196: error: there are no arguments to `GetKeyAgreementAlgorithm' that depend on a template parameter, so a declaration of `GetKeyAgreementAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1197: error: there are no arguments to `GetKeyDerivationAlgorithm' that depend on a template parameter, so a declaration of `GetKeyDerivationAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1198: error: there are no arguments to `GetSymmetricEncryptionAlgorithm' that depend on a template parameter, so a declaration of `GetSymmetricEncryptionAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1199: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h:1200: error: there are no arguments to `GetKeyInterface' that depend on a template parameter, so a declaration of `GetKeyInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::DL_EncryptorBase::Encrypt(CryptoPP::RandomNumberGenerator&, const unsigned char*, unsigned int, unsigned char*) const':
/usr/include/cryptopp/pubkey.h:1230: error: there are no arguments to `GetKeyAgreementAlgorithm' that depend on a template parameter, so a declaration of `GetKeyAgreementAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1231: error: there are no arguments to `GetKeyDerivationAlgorithm' that depend on a template parameter, so a declaration of `GetKeyDerivationAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1232: error: there are no arguments to `GetSymmetricEncryptionAlgorithm' that depend on a template parameter, so a declaration of `GetSymmetricEncryptionAlgorithm' must be available
/usr/include/cryptopp/pubkey.h:1233: error: there are no arguments to `GetAbstractGroupParameters' that depend on a template parameter, so a declaration of `GetAbstractGroupParameters' must be available
/usr/include/cryptopp/pubkey.h:1234: error: there are no arguments to `GetKeyInterface' that depend on a template parameter, so a declaration of `GetKeyInterface' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::HashIdentifier CryptoPP::DL_ObjectImplBase::GetHashIdentifier() const':
/usr/include/cryptopp/pubkey.h:1310: error: non-template `HashIdentifierLookup2' used as template
/usr/include/cryptopp/pubkey.h:1310: error: (use `typename SCHEME_OPTIONS::MessageEncodingMethod::HashIdentifierLookup::template HashIdentifierLookup2' to indicate that it is a template)
/usr/include/cryptopp/pubkey.h:1310: error: declaration does not declare anything
/usr/include/cryptopp/pubkey.h:1311: error: `L' has not been declared
/usr/include/cryptopp/pubkey.h:1311: error: there are no arguments to `Lookup' that depend on a template parameter, so a declaration of `Lookup' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::DL_PublicObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PublicKey&) const':
/usr/include/cryptopp/pubkey.h:1351: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::DL_PrivateObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PublicKey&) const':
/usr/include/cryptopp/pubkey.h:1360: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `void CryptoPP::DL_PrivateObjectImpl::CopyKeyInto(typename SCHEME_OPTIONS::PrivateKey&) const':
/usr/include/cryptopp/pubkey.h:1362: error: there are no arguments to `GetKey' that depend on a template parameter, so a declaration of `GetKey' must be available
/usr/include/cryptopp/pubkey.h: In member function `CryptoPP::PK_MessageAccumulator* CryptoPP::DL_SignerImpl::NewSignatureAccumulator(CryptoPP::RandomNumberGenerator&) const':
/usr/include/cryptopp/pubkey.h:1372: error: there are no arguments to `RestartMessageAccumulator' that depend on a template parameter, so a declaration of `RestartMessageAccumulator' must be available
/usr/include/cryptopp/pubkey.h: In member function `ELEMENT CryptoPP::DL_KeyAgreementAlgorithm_DH::AgreeWithStaticPrivateKey(const CryptoPP::DL_GroupParameters&, const ELEMENT&, bool, const CryptoPP::Integer&) const':
/usr/include/cryptopp/pubkey.h:1481: error: invalid use of undefined type `struct CryptoPP::ModularArithmetic'
/usr/include/cryptopp/integer.h:387: error: forward declaration of `struct CryptoPP::ModularArithmetic'
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const CryptoPP::Integer&)':
/usr/include/cryptopp/pubkey.h:1521: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const typename BASE::KeyClass&)':
/usr/include/cryptopp/pubkey.h:1523: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const CryptoPP::PublicKeyCopier&)':
/usr/include/cryptopp/pubkey.h:1527: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const CryptoPP::PrivateKeyCopier&)':
/usr/include/cryptopp/pubkey.h:1531: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(CryptoPP::BufferedTransformation&)':
/usr/include/cryptopp/pubkey.h:1533: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&)':
/usr/include/cryptopp/pubkey.h:1569: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&)':
/usr/include/cryptopp/pubkey.h:1573: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&, const T4&)':
/usr/include/cryptopp/pubkey.h:1577: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&, const T4&, const T5&)':
/usr/include/cryptopp/pubkey.h:1581: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&, const T4&, const T5&, const T6&)':
/usr/include/cryptopp/pubkey.h:1585: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&, const T4&, const T5&, const T6&, const T7&)':
/usr/include/cryptopp/pubkey.h:1589: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(const T1&, const T2&, const T3&, const T4&, const T5&, const T6&, const T7&, const T8&)':
/usr/include/cryptopp/pubkey.h:1593: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&)':
/usr/include/cryptopp/pubkey.h:1597: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&)':
/usr/include/cryptopp/pubkey.h:1601: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&, const T4&)':
/usr/include/cryptopp/pubkey.h:1605: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&, const T4&, const T5&)':
/usr/include/cryptopp/pubkey.h:1609: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&, const T4&, const T5&, const T6&)':
/usr/include/cryptopp/pubkey.h:1613: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&, const T4&, const T5&, const T6&, const T7&)':
/usr/include/cryptopp/pubkey.h:1617: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
/usr/include/cryptopp/pubkey.h: In constructor `CryptoPP::PK_FinalTemplate::PK_FinalTemplate(T1&, const T2&, const T3&, const T4&, const T5&, const T6&, const T7&, const T8&)':
/usr/include/cryptopp/pubkey.h:1621: error: there are no arguments to `AccessKey' that depend on a template parameter, so a declaration of `AccessKey' must be available
In file included from /usr/include/cryptopp/rsa.h:12,
                 from ClientCredits.h:32,
                 from BaseClient.cpp:47:
/usr/include/cryptopp/asn.h: In member function `void CryptoPP::ASNOptional::DEREncode(CryptoPP::BufferedTransformation&)':
/usr/include/cryptopp/asn.h:224: error: there are no arguments to `get' that depend on a template parameter, so a declaration of `get' must be available
/usr/include/cryptopp/asn.h:225: error: there are no arguments to `get' that depend on a template parameter, so a declaration of `get' must be available
BaseClient.cpp:976:5: warning: #warning Lacks Comment Filtering
BaseClient.cpp:1564:3: warning: #warning ADDME - Import needed
make[2]: *** [amule-BaseClient.o] Error 1
make[2]: Leaving directory `/usr/local/home/kriztofo/src/aMule-2.0.0rc3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/home/kriztofo/src/aMule-2.0.0rc3'
make: *** [all] Error 2
------------------------------------------------------------------------------
end dump
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: stefanero on May 13, 2004, 10:12:49 AM
hey

hmmm just a thought, and not really related
have you tryed to compile a kernel with gcc3.4...?
at the place where I worked last they could not manage to compile a kernel under 3.4 without setting heavy flags...
gcc 3.4 is imo not very compatible to a lot of C code at the moment, or you have to use a lot of C-Flags to get rid of all the new optimisation in hte compiler..
so stick to your well running 3.3.... gcc compiler  ;)

stefanero
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 13, 2004, 08:48:58 PM
The problem is that Crypto++ isn't compiling on GCC3.4 (known Crypto++ bug). AFAIK it's a Crypto++ problem and it's been fixed by someone somewhere, I'll check the url where the fix is and post here.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 13, 2004, 08:50:54 PM
wow, I found it faster than I thought :-D
Here it is: http://sourceforge.net/tracker/index.php?func=detail&aid=862296&group_id=6152&atid=356152

Greetings!
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: kriztofo on May 14, 2004, 08:33:08 AM
Thanks a lot!

I sort of figured it was a problem with Crypto and not aMule, but initial searches (i.e. lazy) for Crypto++ on FM returned a really old release. I am guilty of being a noob and not searching more thoroughly.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: eric666 on May 18, 2004, 02:39:43 PM
Quote
Originally posted by Jacobo221
wow, I found it faster than I thought :-D
Here it is: http://sourceforge.net/tracker/index.php?func=detail&aid=862296&group_id=6152&atid=356152

I've tried this patch before with gcc-3.4 without succes :-(. 1 file doesn't compile (panama.cpp). Is there a patch for this?
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 18, 2004, 08:59:25 PM
No idea, sorry, I'm on GCC 3.3 still so I only know that patch should work (and seem sto work from what I've read on this forums answers after giving the url).
Maybe you are using CVS crypto sources? Just a guess. Sorry, can't help you more. Try downloading Crypto's sources from aMule's download page again and re-apply the patch.
Greetings.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: stefanero on May 18, 2004, 09:36:00 PM
just a shout question,

what does it help if crypto compiles when amule still does not? has anyone tryed to compile amule 1.2.6 under gcc 3.4? I bet this would not even work...

stefanero
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: eric666 on May 19, 2004, 01:07:56 AM
Quote
Originally posted by Jacobo221
No idea, sorry, I'm on GCC 3.3 still so I only know that patch should work (and seem sto work from what I've read on this forums answers after giving the url).
Maybe you are using CVS crypto sources? Just a guess. Sorry, can't help you more. Try downloading Crypto's sources from aMule's download page again and re-apply the patch.
Greetings.

According to the maker of the patch it should work for all source files except panama.cpp.

Quote from http://sourceforge.net/tracker/index.php?func=detail&aid=862296&group_id=6152&atid=356152
This patch causes g++ 3.4 (mainline CVS) to compile
 Crypto++. It also compiles with g++ 3.3, g++ 3.2, and
 g++ 2.95.4. The exception is the file panama.cpp with
 g++ 3.4, which causes an Internal Compiler Error.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 19, 2004, 08:04:39 PM
heh, nice to know I should read to the end ;-P
Search this forums to find some thread on this, though. As I said before, people have made it compile on GCC 3.4 (or at least that's what seems to me from what they answered ;-)). Just post on those threads to them or send them PM to ask them how they did it.
Greetings.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Avi on May 20, 2004, 08:47:42 AM
I'm not sure if this will help ya, but it is worth trying anyway ;)
http://ftp.iasi.roedu.net/mirrors/gentoo.org/distfiles/crypto++-gcc-3.4.diff.bz2
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 20, 2004, 10:31:21 PM
It'd be nice if someone using GCC 3.4 reported if that works.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: linuxuser on May 20, 2004, 11:24:31 PM
:P i´ve compiled amule 1.2.6 with gcc 3.4 on mandrake 10 rc2 amd 64
but cant compile the libcrypto !
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Avi on May 20, 2004, 11:28:19 PM
Quote
Originally posted by linuxuser
:P i´ve compiled amule 1.2.6 with gcc 3.4 on mandrake 10 rc2 amd 64
but cant compile the libcrypto !
Did you try patching crypto with the patch i posted in the link above?  ?(
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: linuxuser on May 20, 2004, 11:32:55 PM
Not yet will try tonight wen i get home !
Avi sorry for asking this but ! how do i aply the patch ? "name of te patch"  patch -pl "file to wich the patch should be aplyed  ?
thanks for the help  :baby:
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Avi on May 20, 2004, 11:46:53 PM
Quote
Originally posted by linuxuser
Avi sorry for asking this but ! how do i aply the patch ? "name of te patch"  patch -pl "file to wich the patch should be aplyed  ?
thanks for the help  :baby:
First, don't be sorry for asking. :)
I'm far from being a Linux guru (I'm a Windows user), but I believe you can apply it by using: patch -p0 < crypto++-gcc-3.4.diff
I didn't check it by myself, but I think that's the correct way...
Someone please correct me if I'm wrong.

Kind regards,
Avi

P.S: For those who wonder... I simply found this patch by using google... I hope it will work.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Kry on May 21, 2004, 12:37:07 AM
Thanks Avi. Looking forward for reports :)
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: linuxuser on May 21, 2004, 07:24:26 PM
it didnt work !!
I've aplyed the patch and tryed make but it gives an error with the libcrypto.cpp
im not if this is the correctc file but i will post the error tonight !
however the error is on a file the patch is not aplyed too !
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Cthulhu on May 22, 2004, 08:45:20 PM
I managed to compile aMule 2.0rc3 and crypto++ with this gentoo patch with GCC 3.4 but it segfault right after i start it. Next I compiled earlier version (aMule 2.0.0rc2) with the same flags/options  and it works.. at least for now.

Oh, yes - I had to unset my CXXFLAGS before compiling crypto++ because of problems with asm in integer.cpp
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Avi on May 24, 2004, 08:49:01 AM
Quote
Originally posted by Cthulhu
I managed to compile aMule 2.0rc3 and crypto++ with this gentoo patch with GCC 3.4 but it segfault right after i start it. Next I compiled earlier version (aMule 2.0.0rc2) with the same flags/options  and it works.. at least for now.

Oh, yes - I had to unset my CXXFLAGS before compiling crypto++ because of problems with asm in integer.cpp
Could you post a gdb backtrace here?
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: eric666 on May 25, 2004, 10:13:59 AM
Quote
Originally posted by Cthulhu
I managed to compile aMule 2.0rc3 and crypto++ with this gentoo patch with GCC 3.4 but it segfault right after i start it.

Yups, I've the same problem, crypto++ (with gentoo patch) and amule compiles with gcc-3.4, but amule segfaults right after the message "this is a new version, locales are reset".

I've played around with compilation flags and now amule works! :D
crypto++: I've unset CFLAGS and CXXFLAGS;
amule: I've add '-fno-unit-at-a-time' to the CFLAGS and CXXFLAGS
I don't know which change makes compilation works.
Title: you got it to compile?
Post by: kriztofo on May 30, 2004, 05:48:09 AM
I still can't get RC3 to compile with gcc 3.4. Now its giving me this error:

In file included from PrefsUnifiedDlg.h:38,
                 from Preferences.h:34,
                 from ListenSocket.cpp:36:
DirectoryTreeCtrl.h:86:3: warning: #warning FIXME!!!!!!!!!!!!!
In file included from Preferences.h:34,
                 from ListenSocket.cpp:36:
PrefsUnifiedDlg.h:81: warning: ISO C++ forbids declaration of `wxChoice' with no type
PrefsUnifiedDlg.h:81: error: expected `;' before '*' token
PrefsUnifiedDlg.h:82: warning: ISO C++ forbids declaration of `wxButton' with no type
PrefsUnifiedDlg.h:82: error: expected `;' before '*' token
PrefsUnifiedDlg.h: In member function `int PrefsUnifiedDlg::GetColorIndex()':
PrefsUnifiedDlg.h:73: error: `pchoiceColor' undeclared (first use this function)
PrefsUnifiedDlg.h:73: error: (Each undeclared identifier is reported only once for each function it appears in.)
ListenSocket.cpp:712:8: warning: #warning Here should be the IDHybrid, but we don't use it yet and I'm afraid it will break a lot ;)
ListenSocket.cpp:718:7: warning: #warning Here should be the IDHybrid, but we don't use it yet and I'm afraid it will break a lot ;)
ListenSocket.cpp:770:6: warning: #warning TODO: CHECK MESSAGE FILTERING!
ListenSocket.cpp:1054:7: warning: #warning We need a new ProcessSharedFileList that can handle dirs.
ListenSocket.cpp:1636:2: warning: #warning OnConnect? ;)
make[2]: *** [amule-ListenSocket.o] Error 1
make[2]: Leaving directory `/usr/local/home/kriztofo/src/aMule-2.0.0rc3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/home/kriztofo/src/aMule-2.0.0rc3'
make: *** [all] Error 2


I am guessing I just need to set some compiler flags but I am unsure which ones. Any ideas?
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Kry on May 30, 2004, 06:53:19 AM
you're using wx 2.5 with rc3, which is not allowed to work at all.
Title: Oops, but also...
Post by: kriztofo on May 30, 2004, 10:21:18 AM
I get a very similar error with the latest cvs, checked out from berlios about 4 hours ago.

In file included from PrefsUnifiedDlg.h:38,
                 from Preferences.h:34,
                 from ListenSocket.cpp:36:
DirectoryTreeCtrl.h:86:3: warning: #warning FIXME!!!!!!!!!!!!!
In file included from Preferences.h:34,
                 from ListenSocket.cpp:36:
PrefsUnifiedDlg.h:81: error: ISO C++ forbids declaration of `wxChoice' with no type
PrefsUnifiedDlg.h:81: error: expected `;' before '*' token
PrefsUnifiedDlg.h:82: error: ISO C++ forbids declaration of `wxButton' with no type
PrefsUnifiedDlg.h:82: error: expected `;' before '*' token
PrefsUnifiedDlg.h: In member function `int PrefsUnifiedDlg::GetColorIndex()':
PrefsUnifiedDlg.h:73: error: `pchoiceColor' undeclared (first use this function)
PrefsUnifiedDlg.h:73: error: (Each undeclared identifier is reported only once for each function it appears in.)
ListenSocket.cpp:585:6: warning: #warning TODO: CHECK MESSAGE FILTERING!
make[2]: *** [amule-ListenSocket.o] Error 1
make[2]: Leaving directory `/usr/local/home/kriztofo/src/amule-cvs/amule-cvs/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/home/kriztofo/src/amule-cvs/amule-cvs'
make: *** [all] Error 2
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 30, 2004, 08:49:39 PM
And are you using wxWdigets 2.4.2 ?
run `wx-config --basename --version` to know.
Greetings!
Title: Wx
Post by: kriztofo on May 31, 2004, 01:02:30 AM
I am running WxWidgets 2.5.1, which I thought cvs was ready to support.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 31, 2004, 01:52:42 AM
> I get a very similar error with the latest cvs
sorry I missed that part :-(
Well, CVS works fine with wx2.5.1 everywhere it's been tried to compile, AFAIK. So maybe the CVS you're trying to compile just doesn't compile :-/ Although that sounds quite strange to me. You could paste the output of this script http://download.berlios.de/amule/get-info.sh and the configure output to give some clues.
Greetings!
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Kry on May 31, 2004, 02:16:34 AM
Are you compiling on mac?
Title: Info dumps
Post by: kriztofo on May 31, 2004, 02:31:01 AM
*Trying to compile on my linux box, running some Slack 8.1 I think.

Get info dump:

I.   Development Environment

     A. Compiler Info
        Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.0/specs Configured with: ../gcc-3.4.0/configure Thread model: posix gcc version 3.4.0

     B. wxWindows Info
        Version: 2.5.1
        -L/usr/local/lib -pthread -lwx_gtk_html-2.5 -lwx_gtk_adv-2.5 -lwx_gtk_core-2.5 -lwx_base_xml-2.5 -lwx_base_net-2.5 -lwx_base-2.5

     C. GTK Info
        GTK 1: 1.2.10
        GTK 2: 2.2.2

II.  System Environment

     A. CPU Info
        Type:  GenuineIntel
        Model: Intel(R) Pentium(R) 4 CPU 1400MHz
        Speed: 1395.790
        BMips: 2719.74
        Flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm

     B. Memory Info
        Total:   513936 kB
        Unused:  251276 kB

     C. Kernel Info
        Version: 2.4.25

     D. Library Info
        wxWindows library: libwx_gtk_xrc-2.5.so (libc6) => /usr/local/lib/libwx_gtk_xrc-2.5.so libwx_gtk_svg-2.5.so (libc6) => /usr/local/lib/libwx_gtk_svg-2.5.so libwx_gtk_stc-2.5.so (libc6) => /usr/local/lib/libwx_gtk_stc-2.5.so libwx_gtk_plot-2.5.so (libc6) => /usr/local/lib/libwx_gtk_plot-2.5.so libwx_gtk_ogl-2.5.so (libc6) => /usr/local/lib/libwx_gtk_ogl-2.5.so libwx_gtk_mmedia-2.5.so (libc6) => /usr/local/lib/libwx_gtk_mmedia-2.5.so libwx_gtk_html-2.5.so (libc6) => /usr/local/lib/libwx_gtk_html-2.5.so libwx_gtk_gizmos-2.5.so (libc6) => /usr/local/lib/libwx_gtk_gizmos-2.5.so libwx_gtk_fl-2.5.so (libc6) => /usr/local/lib/libwx_gtk_fl-2.5.so libwx_gtk_deprecated-2.5.so (libc6) => /usr/local/lib/libwx_gtk_deprecated-2.5.so libwx_gtk_core-2.5.so (libc6) => /usr/local/lib/libwx_gtk_core-2.5.so libwx_gtk_animate-2.5.so (libc6) => /usr/local/lib/libwx_gtk_animate-2.5.so libwx_gtk_adv-2.5.so (libc6) => /usr/local/lib/libwx_gtk_adv-2.5.so libwx_base_xml-2.5.so (libc6) => /usr/local/lib/libwx_base_xml-2.5.so libwx_base_net-2.5.so (libc6) => /usr/local/lib/libwx_base_net-2.5.so libwx_base-2.5.so (libc6) => /usr/local/lib/libwx_base-2.5.so

Configure dump:

kriztofo@bubbles:~/src/amule-cvs/amule-cvs$ ./configure --disable-debug
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for msgfmt... /usr/local/bin/msgfmt
checking for gmsgfmt... /usr/local/bin/msgfmt
checking for xgettext... /usr/local/bin/xgettext
checking for msgmerge... /usr/local/bin/msgmerge
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for strerror in -lcposix... no
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for off_t... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether we are using the GNU C Library 2.1 or newer... yes
checking whether integer division by zero raises SIGFPE... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unsigned long long... yes
checking for inttypes.h... yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for feof_unlocked... yes
checking for fgets_unlocked... yes
checking for getc_unlocked... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getgid... yes
checking for getuid... yes
checking for mempcpy... yes
checking for munmap... yes
checking for putenv... yes
checking for setenv... yes
checking for setlocale... yes
checking for stpcpy... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for strtoul... yes
checking for tsearch... yes
checking for __argz_count... yes
checking for __argz_stringify... yes
checking for __argz_next... yes
checking for iconv... yes
checking for iconv declaration...
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking for nl_langinfo and CODESET... yes
checking for LC_MESSAGES... yes
checking for bison... bison
checking version of bison... 1.35, ok
checking whether NLS is requested... yes
checking whether included gettext is requested... no
checking for GNU gettext in libc... yes
checking for wx-config... /usr/local/bin/wx-config
checking for wxWidgets version >= 2.4.0... yes (version 2.5.1)
checking for wxbase-2.4-config... no
configure:
        WARNING: libwx_base >= 2.4.0 is not found.
        This is not needed for compiling aMule, but it is for compiling amulecmd.
        If you have no wxbase, amulecmd will be linked against wxgtk, thus removing
        all the non-graphical client meaning at all.
        Please check that wxbase-2.4-config is in path, the directory
        where wxWidgets base libraries are installed (returned by
        'wxbase-2.4-config --libs' command) is in LD_LIBRARY_PATH or
        equivalent variable and wxWidgets base is version 2.4.0 or above.
        Or this might also be that your wxbase-config has other name.
        Please try again with --with-wxbase-config=/usr/bin/wxbase-config
        (replace /usr/bin/wxbase-config with a valid path to your wxbase-config)
        * Note:
        Most probably, either one of the above aren't correct, you don't
        have wxbase installed, or are missing wxbase-devel (or equivalent) package.
   
checking for curl >= 7.9.5... yes (version 7.10)
checking if wxWidgets was linked with GTK2... no
checking for gtk-config... /usr/bin/gtk-config
checking for GTK - version >= 1.2.0... yes
checking if wxWidgets version >=2.5.0 ... yes
checking for crypto++ version >= 5.1... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking whether SysTray should be compiled... yes
checking whether SysTray should be compiled in safe mode... no
checking whether pure GTK code should be compiled... yes
checking whether progress bar drawing should be disabled... no
checking for ANSI C header files... (cached) yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for locale.h... (cached) yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for an ANSI C-conforming const... (cached) yes
checking for inline... (cached) inline
checking for off_t... (cached) yes
checking for size_t... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking for sys/time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... yes
checking return type of signal handlers... void
checking whether lstat dereferences a symlink specified with a trailing slash... yes
checking whether stat accepts an empty string... no
checking for strftime... yes
checking for floor... no
checking for ftruncate... yes
checking for gettimeofday... yes
checking for inet_ntoa... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for putenv... (cached) yes
checking for select... yes
checking for setlocale... (cached) yes
checking for sqrt... no
checking for strcasecmp... (cached) yes
checking for strchr... yes
checking for strdup... (cached) yes
checking for strrchr... yes
checking for strstr... yes
checking for strtoul... (cached) yes
checking for getrlimit... yes
checking for setrlimit... yes
checking whether ccache support should be added... no
configure: creating ./config.status
config.status: creating src/Makefile
config.status: creating intl/Makefile
config.status: creating po/Makefile.in
config.status: creating m4/Makefile
config.status: creating Makefile
config.status: creating Compilation.flags
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile


  Configure script has finished system check.

  Configured aMule CVS for 'i686-pc-linux-gnu'.

  Should aMule be compiled in debug mode?                  no
  Should aMule be compiled with release grp code?          no
  Should aMule be compiled without debug reporting?        no
  Should aMule be compiled with profiling?                 no
  Should aMule be compiled with optimizations?             no
  Should aMule be compiled with systray?                   yes
  Should aMule be compiled with safe systray?              no
  Should aMule be compiled with pure GTK code?             yes
  Should aMule be compiled without bar drawing?            no
  Should aMule be linked against patched gsocket?          yes
  Should ccache support be enabled?                        no
  Should aMule command line client be built?               no
  Should aMule GUI client be build?                        no
  Should aMule WebServer be build?                         no
  Should aMule WebServer GUI be build?                     no
  Should aMule ed2k links handler be build?                yes
  Should C aMule Statistics (CAS) be build?                yes
  Crypto++ library/headers style?                          mdk_suse_fc

  Which libraries should aMule use?
                                       wxWidgets          2.5.1
                                       GTK                1.2.10
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Kry on May 31, 2004, 02:42:14 AM
Quote
I get a very similar error with the latest cvs, checked out from berlios about 4 hours ago.

Ah, damm, berlios is not up-to-date. Use the tarballs that are linked on download page.
Title: Re: aMule-2.0.0 RC3 compilation problems with GCC 3.4
Post by: Jacobo221 on May 31, 2004, 03:28:36 AM
lol, not only I didn't notice that it was CVS, but I didn't notice either you were taking it from BerliOS! xDDD
The real _latest_ CVS can be found here: http://amule.hirnriss.net/

Greetings and sorry for all the above, kriztofo

(In fact, anyway, I think berlios's cvs should compile anyway :-P )
Title: Did that, still no luck
Post by: kriztofo on May 31, 2004, 05:11:54 AM
Same exact error with the cvs tarball from the download site. I am thinking maybe this has to do with the wrong headers being included or something.
Title: update
Post by: kriztofo on June 07, 2004, 07:34:04 AM
Well I gave up on gcc 3.4, but I have a suspicion it might have been because wxGTK-2.5.1 was compiled with 3.4

Now I am trying to run amule cvs 0606 compiled with gcc 3.3.4. It compiles fine but now I get a segfault when amule starts up.

Backtrace:

kriztofo@bubbles:/download/edonkey$ amule
Initialising aMule
22701gifile is 0-size, not added
a.out is 0-size, not added
*** UDP socket at 4665
*** TCP socket at 4662
*** UDP socket at 4665

OOPS! - Seems like aMule crashed
--== BACKTRACE FOLLOWS: ==--

[0x4055d198]
[2] /lib/libpthread.so.0 [0x40a7c144]
[3] /lib/libc.so.6 [0x40ab2288]
[4] /lib/libc.so.6 [0x40af82fa]
[5] /lib/libc.so.6(malloc+0xe0) [0x40af7ae4]
[6] /usr/local/lib/libstdc++.so.6(_Znwj+0x2e) [0x40a1f1ce]
[7] amule(_ZN18CClientCreditsList8LoadListEv+0x707) [0x815d8d7]
[8] amule(_ZN18CClientCreditsListC1EP12CPreferences+0x41) [0x815cf75]
[9] amule(_ZN9CamuleApp6OnInitEv+0x1f8d) [0x8295095]
[10] amule(_ZN12wxAppConsole10CallOnInitEv+0x18) [0x8299c24]
[11] /usr/local/lib/libwx_base-2.5.so.1(_Z7wxEntryRiPPc+0x45) [0x40501cc5]
[12] amule(main+0x22) [0x8292d68]
[13] /lib/libc.so.6(__libc_start_main+0xbd) [0x40aa117d]
[14] amule(_ZNK15wxCmdLineParser5FoundERK8wxStringPS0_+0x31) [0x813e611]
Aborted