aMule Forum
English => en_Linux => Topic started by: genghiskhano on December 17, 2005, 01:15:56 PM
-
Hello,
I've installed Amule and it doesn't open if I do it from the command line I get the following error:
amule: error while loading shared libraries: libbfd-2.15.94.0.2.2.so: cannot open shared object file: No such file or directory
when I was trying to install it I was getting dependecies warinigs but I sorted out before I installed it, the installation run without any problems ,
HELP ME PLEASE.
Thank you
-
Wrong package (was probably built for SuSE 9.3), remove it and use this one:
http://packman.links2linux.de/?action=574
-
Try the RPMS made by IhmSelbst: ed2k-serverboard.de/downloads/ihmselbst/rpm/SuSE/10.0/amule
-
Or that, they are equivalent (same libraries). But IhmSelbst's one doesn't have everything enabled, PackMan's one does.
-
hello again, thank you for your help, no I get this:
#### YaST2 conflicts list - generated 2005-12-14 21:32:54 ####
wxGTK 2.6.1.0-4 conflict
Required by:
aMule requires libwx_baseu-2.6.so.0
aMule requires libwx_baseu_net-2.6.so.0
aMule requires libwx_baseu_xml-2.6.so.0
aMule requires libwx_gtk2u_adv-2.6.so.0
aMule requires libwx_gtk2u_core-2.6.so.0
aMule requires libwx_gtk2u_html-2.6.so.0
aMule requires libwx_gtk2u_qa-2.6.so.0
aMule requires libwx_gtk2u_xrc-2.6.so.0
Conflict Resolution:
( ) Do Not Set wxGTK to Protected
( ) Remove the Referring Package
Do Not Install aMule
( ) Ignore Conflict and Risk System Inconsistencies
#### YaST2 conflicts list END ###
any ideas?
-
ARGH! Again the *junk* wx package library hell!
You have some junk wx libraries from somewhere on your system. Please do the next things in a terminal (no YaST):
Remove the previously installed aMule package:
rpm -e aMule --nodepsThen remove the junk wx package:
rpm -e wxGTK --nodepsThen install this working wx package:
rpm -Uvh ftp://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS/inst-source/suse/i586/wxGTK-2.6.1.0-4.i586.rpmAnd finally install the aMule package again:
rpm -Uvh ftp://packman.iu-bremen.de/suse/10.0/i586/aMule-2.0.3-1.pm.3.i586.rpm
-
thank you very much dudes that did it, this must be the fastest forum ever , I haven't finished typing my message and I have an answer :D
-
Originally posted by Gerd78
... But IhmSelbst's one doesn't have everything enabled, ...
what? - iirc, there should be enabled the same things in the SuSE10.0-package, as were standard in the official 2.0.3-rpm for SuSE9.3 (perhaps one should "define" a kind of "standard", what a package should contain or what?)
btw:
if required, one could (rebuild and) offer an "official" package for here, but we also can continue sending ppl to packman´s. - now, as he supports SuSE10.0-packages as well, and if there is no need to offer mine any longer, i have no problems to remove it, if no longer requested.
cu
-
Originally posted by IhmSelbst
iirc, there should be enabled the same things in the SuSE10.0-package, as were standard in the official 2.0.3-rpm for SuSE9.3
There are 10 executables:
alc
alcc
amule
amulecmd
amuled
amulegui
amuleweb
cas
ed2k
wxcas
PackMan's RPM has all of them, yours doesn't seem to have amuled + amulegui. This doesn't mean that everyone should enable them, I just mentioned the difference.
Originally posted by IhmSelbst
perhaps one should "define" a kind of "standard", what a package should contain or what?
That's difficult to do - the most common solution with binary packages is to enable everything. Maybe with subpackages for optional things.
Originally posted by IhmSelbst
if required, one could (rebuild and) offer an "official" package for here, but we also can continue sending ppl to packman´s.
Hm... My idea was following:
- Reduce the total amount of binary packages to avoid confusion, duplication etc.
- If there's a problem with existing packages (bad configuration etc.), contact the packager and explain the situation so he can improve it instead of creating a new one
PackMan is a well-known resource for SuSE users, so I think it makes sense to bundle the efforts there. The only problem is that they do releases only, no CVS builds. Another advantage with PackMan's repository is that it supports YaST, apt4rpm and yum.
So my suggestion would be:
- Let PackMan do the packages for released versions - they have mirrors, disk space, bandwidth en masse etc. + x86_64 hardware(!)
- If PackMan does something wrong, write to him (Quentin Denis) + attach a patch that fixes the problem
- Send people to you if they want CVS binaries
What do you think about this idea?
As far as it concerns wx stuff: There's no need to worry about that, I think. For SuSE 10.0, SuSE's RPM is fine and for earlier versions, aMule's ./configure will stop anyway so people won't end up with old/unstable/broken ones.
-
Originally posted by Gerd78
Originally posted by IhmSelbst
iirc, there should be enabled the same things in the SuSE10.0-package, as were standard in the official 2.0.3-rpm for SuSE9.3
There are 10 executables:
alc
alcc
amule
amulecmd
amuled
amulegui
amuleweb
cas
ed2k
wxcas
yep. and a simple "rpm -qlvp http://www.ed2k-serverboard.de/downloads/ihmselbst/rpm/SuSE/10.0/amule/aMule-2.0.3-1.i686-SuSE_10.0.rpm"
lists them all. - seems, i´m not so forgetful, as believed. :P
will check out the rest lateron, must leave again soon.
cu