SliTaz Forum
You are not logged in.
Pages: 1
Hello,
Last week, I made some updates after 3 weeks without using SliTaz (cooking 32bits):
019-02-22 21:42:33 - Installed - asunder (2.9.3) - 83b9d08b6f5c4cc477b06e6c124941d7
2019-02-22 21:42:37 - Installed - attr (2.4.48) - 384ce31614ba841a1e9849755acba949
2019-02-22 21:42:52 - Installed - busybox (1.30.1) - 5ae24a741d7201952501e177b1ac61e4
2019-02-22 21:42:58 - Installed - cairo (1.16.0) - 512f9434a08480248f0c6d2cc8f9ab08
2019-02-22 21:43:10 - Installed - cryptopp (8.0.0) - cc940eb7e911c092376b9a20ac4de8b0
2019-02-22 21:43:15 - Installed - dialog (1.3_20190211) - fca75e8c242c37b53b0e6259ca6fdb7f
2019-02-22 21:43:20 - Installed - slitaz-boot-scripts (453) - 9b6f5b545986a390824dd779a6a54ac9
2019-02-22 21:43:23 - Reconfigured - ipxe (944)
2019-02-22 21:43:23 - Reconfigured - memtest (944)
2019-02-22 21:43:23 - Installed - syslinux (4.06) - 695f1761ff47f75c2f429d11f422fc17
2019-02-22 21:43:28 - Installed - syslinux-extra (4.06) - 7e5f36dd00ea8b9a26ebc93b7f34b57a
After the updates, aMule doesn't start anymore.
How can I solve the problem?
Thank you for your help!
Offline
This is the error message in a terminal:
cedric@R8:~$ amule
amule: Symbol `_ZTVN8CryptoPP13BaseN_EncoderE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP9FileStoreE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP6SHA256E' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP6FilterE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP22BufferedTransformationE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP18HashTransformationE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP5StoreE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP8DES_EDE34BaseE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP11StringStoreE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP6SourceE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP9PK_SignerE' has different size in shared object, consider re-linking
amule: Symbol `_ZTVN8CryptoPP23FilterWithBufferedInputE' has different size in shared object, consider re-linking
amule: symbol lookup error: amule: undefined symbol: _ZN8CryptoPP21g_pAssignIntToIntegerE
cedric@R8:~$
Offline
Downgrade by installing cryptopp-5.6.1 from your package cache, this should re-enable amule.
Then block cryptopp from upgrade in tazpkg.
The issue is due to cryptopp being upgraded to 8.0 with new API,amule-2.3.2 won't run or build against that version.
Pascal the slitaz manager can decide how to resolve the issue.
http://www.mediafire.com/file/wsarvkdjglsb5m5/cryptopp-5.6.1.tazpkg
Offline
Thank you mojo, it works with your solution!
But I hope the issue will be solved (by Pascal) so that I can unlock the package.
Offline
The package amule is now recompiled to work with cryptopp 8.0.0
Offline
Hello HGT,
Thank you for your answer!
A few minutes ago, I tried to update the package "amule" with the package manager, but there is no update available. I suppose that it will be available soon.
Offline
@R8
Pascal Bellard controls the movement of packages from cook.slitaz.org(build server) to mirror1.slitaz.org(repository).
Until the new package is moved to the repository and the database files are refreshed you will not see the update in tazpkg.
The new package can be downloaded now by going to cook.slitaz.org/cooker.cgi?pkg=amule and clicking the download link.
Offline
It's now OK. Thank you everybody.
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]